Issue #602 resolved

ETag autotags are incorrect on 304

Robert Brewer
created an issue

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.

Comments (2)

  1. Log in to comment