USE_ETAGS returns status 304 even if response.status_code=400
|Reported by:||mihai.preda@…||Owned by:||adrian|
|Cc:||Triage Stage:||Ready for checkin|
|Has patch:||yes||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
a page which wants to return a 400 status code (by setting response.status_code=400),
may return a 304 status code on reloads (because the content of the page didn't change).
I don't know if this is the correct behavior or not, but I find it surprising that a 400-status is transformed into a 304-status.
I would expect USE_ETAGS to only affect pages with 200 status code (or something like it).
Change History (13)
comment:4 Changed 9 years ago by Michael Radziej <mir@…>
- Triage Stage changed from Unreviewed to Accepted
Changed 9 years ago by Vinay Sajip <vinay_sajip@…>
comment:7 Changed 9 years ago by Vinay Sajip <vinay_sajip@…>
- Triage Stage changed from Accepted to Ready for checkin
comment:8 Changed 8 years ago by mtredinnick
- Resolution set to fixed
- Status changed from new to closed
comment:9 Changed 8 years ago by Manuel Saelices <msaelices@…>
- Resolution fixed deleted
- Status changed from closed to reopened