#6552: django.core.context_processors.auth causes "Vary: Cookie" header no 
matter
what
-------------------------------------+--------------------------------------
          Reporter:  o...@iola.dk    |         Owner:  lukeplant
            Status:  closed          |     Milestone:           
         Component:  Authentication  |       Version:  SVN      
        Resolution:  fixed           |      Keywords:           
             Stage:  Accepted        |     Has_patch:  1        
        Needs_docs:  1               |   Needs_tests:  0        
Needs_better_patch:  0               |  
-------------------------------------+--------------------------------------
Changes (by lukeplant):

  * status:  reopened => closed
  * resolution:  => fixed

Comment:

 I cannot reproduce.  I started a new project, which has the session
 framework and middleware turned on by default, and I modified the view so
 that it actually uses `RequestContext`:
 {{{
 #!python
 from django.template import Template, RequestContext
 from django.http import HttpResponse

 def some_view(request):
     return HttpResponse(Template("Hello,
 world.").render(RequestContext(request)))
 }}}

 With this view I get:
 {{{
 $ curl -i http://localhost:8000/
 HTTP/1.0 200 OK
 Date: Sat, 27 Feb 2010 17:40:23 GMT
 Server: WSGIServer/0.1 Python/2.5.4
 Content-Type: text/html; charset=utf-8

 Hello, world.
 }}}


 If I change the template to `"Hello, {{ user }}", I get:
 {{{
 $ curl -i http://localhost:8000/
 HTTP/1.0 200 OK
 Date: Sat, 27 Feb 2010 17:42:22 GMT
 Server: WSGIServer/0.1 Python/2.5.4
 Vary: Cookie
 Content-Type: text/html; charset=utf-8

 Hello, AnonymousUser
 }}}

 So it seems to be working correctly.  I see this both with current trunk
 and with the 1.2 beta 1 (revision 12394) .  Please re-open if you can
 provide more details that will demonstrate your bug.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/6552#comment:19>
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.

Reply via email to