For several months, we have been caching views using the URLconf method (urls.py). An entry from urls.py is below as an example:
url(r'^(?P<path>.*)/content/(?P<id>[-\w]+)/$$', cache_page (hierarchies.views.category_content_detail, CACHE_TIMEOUT), name='category_content_detail'), Recently, we had a need to add variance of cache based on cookie value to support some personalization features. After reading the django docs, it seemed easy enough to add the @vary_on_cookie decorator to appropriate views. @vary_on_cookie def category_content_detail(request, path, id): .. .. What I've noticed, is that since adding this vary decorator, the page is no longer caching, as seen by monitoring logs and seeing many backend processes firing which normally do not fire when the page is cached. Any ideas on why I'd see this behavior? My browser is setting the cookie value appropriately, as I've monitored in Firebug, but I'm just not seeing any sort of caching taking place. Upon removing the vary_on_cookie decorator, caching returns to normal. What I have noticed in testing is this. If I go back to a pure pre- view cache setup: @vary_on_cookie @cache_page(60 * 15) def category_content_detail(request, path, id): Is there a way to use vary_on_cookie with the URLconf like setup? I like the flexibility of the URLConf method and but also need the vary features. Reference: http://docs.djangoproject.com/en/dev/topics/cache/#specifying-per-view-cache-in-the-urlconf
-- 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.
