Hi! If a core developer would take a look at
http://code.djangoproject.com/ticket/6552 and indicate whether the approach is the right one, that would be great. Short version of the story: using django.core.context_processors.auth is the same as saying "all pages depend on who is currently logged in", meaning a Vary: cookie header is always emitted on all pages, meaning no upstream caching including reverse proxies like Varnish for any pages if visitors happen to have unique cookies, which they will with Google Analytics. And admin has a hard-coded dependency on the context processor. So admin + Google Analytics = no caching. There's a simple suggestion for fixing things in the issue, and I don't mind writing the missing documentation if there's consensus it's the right approach. Maybe we can get it fixed in Django 1.2. Ole --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
