#11479: cache_page and last_modified decorators can't be used together ----------------------------------+----------------------------------------- Reporter: megaman...@gmail.com | Owner: nobody Status: new | Milestone: Component: Cache system | Version: 1.0 Keywords: | Stage: Unreviewed Has_patch: 0 | ----------------------------------+----------------------------------------- The function the calculates the last_modified date will always run but since the cache_page decorator ends up calling a middleware it will get to the last_modified and etag headers first. It will see that they are empty (because only another middleware could have changed them at that point) and then set them to default values. Then the last_modified decorator will see the last modified header is already set and not change it.
-- Ticket URL: <http://code.djangoproject.com/ticket/11479> 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-updates@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 -~----------~----~----~----~------~----~------~--~---