#3206: USE_ETAGS returns status 304 even if response.status_code=400
-------------------------------------+--------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: adrian
Status: new | Component: Core framework
Version: SVN | Resolution:
Keywords: rev 4235 | Stage: Unreviewed
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
-------------------------------------+--------------------------------------
Comment (by [EMAIL PROTECTED]):
In RFC 2616, section 10.3.5, 304 Not Modified:
"If the client has performed a conditional GET request and access is
allowed, but the document has not been modified, the server SHOULD respond
with this status code (304)."
I see two conditions for 304: GET, and "access is allowed". I interpret
"access is allowed" as meaning: 2xx status code.
Also it is obvious (IMO) that not any status code (e.g. 4xx, 5xx) may be
replaced with 304, as this would effectively erase this significant
information (the status code).
I would suggest to play it conservativelly and only rewrite 200 to 304,
unless some more authoritative understanding of RFC 2616 is expressed.
--
Ticket URL: <http://code.djangoproject.com/ticket/3206#comment:3>
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
-~----------~----~----~----~------~----~------~--~---
