Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

304 Required Headers #61

Closed
mnot opened this Issue · 3 comments

2 participants

@mnot
Owner

Check to make sure the required headers are there on 304s; response_analyse

@mnot
Owner

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
response.

@mnot mnot closed this in 2d088f1
@barryhunter

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
http://webmasters.stackexchange.com/questions/25520/should-304-not-modified-responses-include-the-last-modified-header

  • before I found this github project.

The rest of your required headers are allowed by apache.

@mnot
Owner

Fixed, as mentioned on stack exchange. Thanks again!

@barryhunter barryhunter referenced this issue from a commit in barryhunter/geograph-project
barry Revert r7560 - turns out it was a bug in redbot. It was misdiagnosing…
… an issue.

mnot/redbot#61
e6d9dd2
@barryhunter barryhunter referenced this issue from a commit in barryhunter/geograph-project
barry Revert r7560 - turns out it was a bug in redbot. It was misdiagnosing…
… an issue.

mnot/redbot#61
eb43101
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.