In order to force a response body despite conditional cache header values, as is appropriate per rfc. see: http://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html#sec13.2.6
I agree that this would be great. I'm having a tough time how to prevent express from sending a 304 when I don't want it to.
My requests are '"Cache-Control:max-age=0" and "Pragma:no-cache" but still come back with 304s.
For my json api, this means that link headers are not getting through and so pagination is failing.
check for no-cache cache request directive
include unit test for no-cache closes #2
Any chance of getting this pulled?
@ggoodman that brings up a good point though, because we should be hashing header fields as well for the etag
Check for no-cache cache request directive