I would like to make my first contribution to the Django code, but these
both are pretty easy and at least to me seem pretty obvious, so I thought
there might be some good reason they have not yet already been done.
Depending on the response, I would do these in different ways as well, so I
wa
On Thursday 25 July 2013 08:37:06 Russell Keith-Magee wrote:
>
> Could I get you to open this as a ticket so that it isn't forgotten?
>
https://code.djangoproject.com/ticket/20814
Thanks,
Shai.
--
You received this message because you are subscribed to the Google Groups
"Django develo
Hi everybody,
TL;DR: A simple change can make Django's CSRF protection a little better; an
additional, slightly less simple one, can also make it look better.
Django's CSRF protection scheme is a bit unusual; unlike most such schemes, it
does not rely on a value stored in the server that needs
Hi Justin,
On Sat, Jul 27, 2013 at 11:17 PM, Justin Michalicek
wrote:
> I would like to make my first contribution to the Django code, but these
> both are pretty easy and at least to me seem pretty obvious, so I thought
> there might be some good reason they have not yet already been done.
> Dep
Awesome, thank you. I am guessing it is preferred that these be done as
two separate tickets and patches since they are technically separate
features. I'm not seeing an obvious way to mark one as relying on another,
though. Should I just note in the trac ticket for #2 that it relies on #1
wh