#6552: django.core.context_processors.auth causes "Vary: Cookie" header no
matter
what
-------------------------------------+--------------------------------------
Reporter: o...@iola.dk | Owner: lukeplant
Status: reopened | Milestone:
Component: Authentication | Version: SVN
Resolution: | Keywords:
Stage: Accepted | Has_patch: 1
Needs_docs: 1 | Needs_tests: 0
Needs_better_patch: 0 |
-------------------------------------+--------------------------------------
Changes (by harm):
* status: closed => reopened
* resolution: fixed =>
Comment:
It seems its not fixed, or reintroduced...
I see Vary: Cookie headers appearing on views that don't touch the session
at all.
Which makes it impossible in practice to cache these, either by (reverse)
proxies nor by (most) browsers.
version: Django-1.2-beta-1
==== steps to reproduce ====
- enable session framework
- use django.core.context_processors.auth
write a simple view:
{{{
#!python
def some_view(request):
return HttpResponse("Hello, world. You're at the poll index.")
}}}
==== result ====
This view '''always''' get a {{{Vary: Cookie}}} header set by django
[[br]]
this page then '''never''' gets cached by most browsers (even firerfox),
not even when adding a {{{max-age=14400}}} cache-control header.
==== expected ====
any view, not touching the session, should not get a Vary: Cookie http
header.
--
Ticket URL: <http://code.djangoproject.com/ticket/6552#comment:18>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
