Ticket #602 (defect)
Opened 2 years ago
Last modified 2 years ago
ETag autotags are incorrect on 304
Status: closed (wontfix)
| Reported by: | fumanchu | Assigned to: | rdelon |
|---|---|---|---|
| Priority: | normal | Milestone: | 3.0 |
| Component: | CherryPy code | Keywords: | |
| Cc: |
The ETag response header should be the same for a given resource regardless of whether you receive a 200 OK or 304 Not Modified response. They aren't, currently, because the autotags feature uses a hash of the response body, and when 304 is raised, the response body is emptied, and the ETag hash is therefore different. Fixing this will require caching ETag headers across requests, possibly in the filesystem in order to support deployments on multiprocess HTTP servers.
Change History
11/22/06 13:47:05: Modified by fumanchu
- status changed from new to closed.
- resolution set to wontfix.
This isn't worth the effort to programatically provide or deny. Warning added to docstring in [1445].