Changes between Initial Version and Version 1 of Ticket #19604, comment 3
- Timestamp:
- Jan 26, 2013, 7:00:27 AM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #19604, comment 3
initial v1 1 This a well-know behavior of HTTP.1 This a well-known behavior of HTTP. 2 2 3 3 If your application requires caching with sub-second precision, then you should use ETags (USE_ETAGS = True) and disable [https://docs.djangoproject.com/en/dev/ref/middleware/#module-django.middleware.http ConditionalGetMiddleware]. ETags were added to the HTTP protocol precisely to cater for the use case you're describing. In Django they are handled by [https://docs.djangoproject.com/en/dev/ref/middleware/#module-django.middleware.common CommonMiddleware].