Here's a stick to whack this with: NoVarySessionMiddleware - http://github.com/jbalogh/commonware
On Aug 26, 2:15 pm, jfenton <jsfen...@gmail.com> wrote: > I'm using 1.1.1. I've got a bunch of legacy code written with date- > based generic views: django.views.generic.date_based . I think that > these views set avary:Cookieheader, which messes up my upstream > caching (see related ticket:http://code.djangoproject.com/ticket/13285 > ) > > Thevary:Cookieheader isn't needed on these pages (the content > doesn't actuallyvary) but I'm not sure how to get rid of it. Trying > to set thevaryheader in the view only adds a differentvaryheader, > i.e. doing this: > > response = object_detail(request, .... > response['Vary'] = "other junk" > return response > > results inVarybeing set to both "cookie" and "other junk". > > Is there a straightforward way make thevary:cookieheader go away > without breaking too many dishes? I can probably work around this at > the cache level, but it would be much cleaner not to... > > Thanks for any suggestions. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
