Check to make sure the required headers are there on 304s; response_analyse
A 304 response MUST include a Date header field (Section 9.2 of
[Part2]) unless the origin server does not have a clock that can
provide a reasonable approximation of the current time. If a 200
response to the same request would have included any of the header
fields Cache-Control, Content-Location, ETag, Expires, Last-Modified,
or Vary, then those same header fields MUST be sent in a 304
Check for required headers on 304 responses; fixes #61.
Should the Last-Modified be included in this check?
I've run into this report on redbot recently, and so tried to modify my source to include the header (thought it wouldnt be required - because the date is already in the "if-modified-since" so the client knows it) - it didnt work.
... found that Apache is stripping the Last-Modified header. So the header is not included in the response.
I posted to the redbot mailing list - but its on hold for moderation. And I posted it here
The rest of your required headers are allowed by apache.
Fixed, as mentioned on stack exchange. Thanks again!
Remove Last-Modified from required headers on 304 and 206 (#61).
Revert r7560 - turns out it was a bug in redbot. It was misdiagnosing…
… an issue.