#5047: max-age set by cache_page is overwritten by cache_middleware
--------------------------------------------------------------+-------------
Reporter: permon |
Owner: jacob
Status: new |
Component: Cache system
Version: SVN |
Resolution:
Keywords: cache_control, cache, middleware, sprintsept14 |
Stage: Ready for checkin
Has_patch: 1 |
Needs_docs: 0
Needs_tests: 0 |
Needs_better_patch: 0
--------------------------------------------------------------+-------------
Comment (by permon):
Replying to [comment:10 jacob]:
> Yeah, that's looking more like what I had in mind -- thanks!
I've thinked little bit more about it and here are (i think) typical
usecases:
* I don't have cache middleware. Everything is ok
* I have cache middleware with some caching time e.g. 300 seconds
* * I have some special view, which could be cached for one hour, I'll
use @cache_page decorator with 60*60
* * I have another special view which should be cached only for ten
seconds. Again simplest way is to use decorator with parameter 10
In last two cases is important, that I need to _rewrite_ default
behaviour. So, the first patch solves the problem in most expected way.
Otherwise (with min value) will be always one of these cases unreachable.
--
Ticket URL: <http://code.djangoproject.com/ticket/5047#comment:11>
Django Code <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 [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
