#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 Dart):
So as i see there two posible solutions:
- remove generation etag from middleware if empty content exists
or
- add one more attributes for generation etag
No matter from rfc-7232:
An origin server SHOULD send an ETag for any selected representation
for which detection of changes can be reasonably and consistently
determined, since the entity-tag's use in conditional requests and
evaluating cache freshness ([RFC7234]) can result in a substantial
reduction of HTTP network traffic and can be a significant factor in
improving service scalability and reliability.
Or we can do nothing and rely on customer understanding
--
Ticket URL: <https://code.djangoproject.com/ticket/30812#comment:7>
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.010e9bd770f7a8f6b24ab85ef15d0c75%40djangoproject.com.
