Cache-control information in 304 response about cachecow HOT 5 CLOSED

This behaviour is correct. Please see Issue #36.

from cachecow.

Hi Ali,

In that case, should we just remove them? Because according to RFC2616, Section 10.3.5, Cache-Control, Expires and Pragma should not be sent back:

The response MUST include the following header fields:

• Date, unless its omission is required by section 14.18.1 (This is correct)
• ETag and/or Content-Location, if the header would have been sent in a 200 response to the same request (this is correct)
• Expires, Cache-Control, and/or Vary, if the field-value might differ from that sent in any previous response for the same variant (We should not send them back as they haven't changed).

Thanks for your patience.

from cachecow.

And if you look at http://stackoverflow.com/questions/1587667/should-http-304-not-modified-responses-contain-cache-control-headers/4393499#4393499. There is an answer by Mark Nottingham said:

HTTPbis updates RFC2616 to say:

A 304 response MUST include a Date header field (Section 9.3 of [Part1]) unless its omission is required by Section 9.3.1 of [Part1]. 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.

I think it is a safe option to send the original headers back.

Thanks

from cachecow.

Thanks @melcloud I will take this one up to fix.

from cachecow.

It is actually ASP.NET Web API adding these headers not me.

from cachecow.