> Better would be to open a ticket at code.djangoproject.com and then take this
> up on django-developers.
Done (ticket #3285), and done. Is that the normal procedure, then, for
contrib apps? The note on the bottom of the contrib add-on page says to
take it up here, which is what I did. However,
On 1/11/07 8:58 AM, Jeremy Dunck wrote:
> On 1/10/07, Gulopine <[EMAIL PROTECTED]> wrote:
> ...
>> The code for middleware.py follows (I've placed it in
>> django.contrib.signed_cookies, but any other name would suffice):
>>
>
> This looks useful, but please re-send the code as an attachment to
On 1/10/07, Gulopine <[EMAIL PROTECTED]> wrote:
...
> The code for middleware.py follows (I've placed it in
> django.contrib.signed_cookies, but any other name would suffice):
>
This looks useful, but please re-send the code as an attachment to
avoid email line wrap munging. :)
In response to some discussion on Chapter 20 of the Django book, I'd
like to submit my first contrib package for consideration, a middleware
package that transparently implements signed cookies. It uses the
SECRET_KEY setting already included in Django, and could easily be
modified to allow
4 matches
Mail list logo
