On Jun 5, 6:22 pm, Peter Rowell <[EMAIL PROTECTED]> wrote: > > does per-view or template fragment caching override that? > > From looking at django/middleware/cache.py, I would say that the view > (and therefore the template) never get a chance to override. This > check is done early in the request processing cycle, even before URL > routing is performed.
That's what I suspected. Is there any way to override or modify that behavior? Perhaps with the cache-control header? Or should I toss out anonymous_only and go through all my stuff caching what I can? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
