To post to this group, send email to django-developers@googlegroups.com.
>> To unsubscribe from this group, send email to
>> django-developers+unsubscr...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/django-developers?hl=en.
>>
unsubscribe from this group, send email to
> django-developers+unsubscribe@**googlegroups.com
> .
> For more options, visit this group at http://groups.google.com/**
> group/django-developers?hl=en<http://groups.google.com/group/django-developers?hl=en>
> .
>
>
>
--
*
ir examples, they are hand-crafting
the HTTP request to spoof this but I guess that is not representative of
what can be done via a browser-based CSRF attack. How much of a security
issue is this?
I'm happy to share the relevant pages of the report if anyone's interested.
All thoughts a
further.
On Sun, Nov 13, 2011 at 7:05 PM, Yo-Yo Ma wrote:
> Before voting for more magic to the transaction middleware, I'd vote
> to remove it altogether. Explicit is surely better than implicit in
> this case. The admin already uses commit_on_success, etc.
>
> On Oct 18,
is is sensible.
--
*Dr. David Winterbottom*
Head of Programming
Tangent Labs
84-86 Great Portland Street
London W1W 7NR
England, UK
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to dj
