#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: Accepted
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
-------------------------------------+--------------------------------------
Changes (by Vinay Sajip <[EMAIL PROTECTED]>):
* has_patch: 0 => 1
Comment:
Patch added to only return a 304 when the original status was 200 and the
ETag matches. Possibly any 2xx return should be treated this way, but I've
gone with just 200 for now.
--
Ticket URL: <http://code.djangoproject.com/ticket/3206#comment:6>
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
-~----------~----~----~----~------~----~------~--~---
