#32531: Cache key not learnt for 304 responses — view must keep redoing work
until
"fresh" request comes in!
------------------------------------+--------------------------------------
Reporter: Nathan Vander Wilt | Owner: nobody
Type: Uncategorized | Status: new
Component: HTTP handling | Version: 3.1
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------------+--------------------------------------
Comment (by Nathan Vander Wilt):
Ah, I should note that my MIDDLEWARE ordering is:
{{{
[
'UpdateCacheMiddleware',
# … snip …
'ConditionalGetMiddleware',
# … snip …
'FetchFromCacheMiddleware'
]
}}}
Perhaps that is incorrect? Is ConditionalGet intended to come **after**
FetchFromCache or will that cause different problems?
--
Ticket URL: <https://code.djangoproject.com/ticket/32531#comment:1>
Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.1d05f0b8f81072978154bada99b24f67%40djangoproject.com.
