Re: Django 1.4 bug: Using cache_page and csrf_protect decorators results in a messy Set-Cookie response header.

2012-05-14 Thread Suteepat Damrongyingsupab
On Mon, May 14, 2012 at 1:25 PM, Rafał Stożek wrote: > >> Could you try again to cause bug with SafeView class, but this time using >> TemplateResponse class instead of render_to_response shortcut? >> >> >> On Mon, May 14, 2012 at 10:24 AM, Suteepat Damrongyingsu

Re: Django 1.4 bug: Using cache_page and csrf_protect decorators results in a messy Set-Cookie response header.

2012-05-14 Thread Suteepat Damrongyingsupab
talled version of 1.3? Does your code pickle or unpickle > sessions or cookies anywhere outside of the caching framework? > > I thought we fixed that bug, but if you can provide minimal steps to > reproduce it in Django 1.4, we'll have to reopen the ticket. > > -Paul >

Django 1.4 bug: Using cache_page and csrf_protect decorators results in a messy Set-Cookie response header.

2012-05-12 Thread Suteepat Damrongyingsupab
I'm using Django 1.4. According to the Django csrf docs, I decorate my class-based view in the urls.py as follows: cache_page(1800)(csrf_protect(MyView.as_view())) I kept reloading MyView page url and Set-Cookie header would be recursive like this: Set-Cookie: csrftoken="Set-Cookie: csrftoke