#30812: ConditionalGetMiddleware returns 304 if ETag is the same but
Last-Modified
has changed.
-------------------------------------+------------------------------------
Reporter: Flavio Curella | Owner: Dart
Type: Bug | Status: assigned
Component: Core (Cache system) | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+------------------------------------
Comment (by Claude Paroz):
One possible solution would be to not generate an Etag for empty content.
I didn't find documentation about that specific case, but for me, it does
not make much sense to cache (return 304) empty responses.
As for the precedence between Etag and Last modified conditions, I think
Django is respecting the specs.
--
Ticket URL: <https://code.djangoproject.com/ticket/30812#comment:6>
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/066.8ce929d8cbcaf7030ae1c52787cef3e3%40djangoproject.com.
