On Wed, Sep 1, 2010 at 4:39 PM, Maxim Dounin <span dir="ltr"><<a href="mailto:mdounin@mdounin.ru">mdounin@mdounin.ru</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hello!<br>
<div class="im"><br>
On Wed, Sep 01, 2010 at 01:23:38PM -0700, kevin wrote:<br>
<br>
> i want nginx to include ContentType text/css for css files in 304 Not<br>
> Modified request<br>
><br>
> here is the headers for the static css file request. you can see that there<br>
> is no ContentType sent.<br>
<br>
</div>RFC 2616 says about 304 responses:<br>
(<a href="http://tools.ietf.org/html/rfc2616#section-10.3.5" target="_blank">http://tools.ietf.org/html/rfc2616#section-10.3.5</a>)<br>
<br>
If the conditional GET used a strong cache validator (see section<br>
13.3.3), the response SHOULD NOT include other entity-headers.<br>
Otherwise (i.e., the conditional GET used a weak validator), the<br>
response MUST NOT include other entity-headers; this prevents<br>
inconsistencies between cached entity-bodies and updated headers.<br>
<br>
Content-Type is entity header and not listed above this paragraph,<br>
so clearly qualifies as "other entity-headers".<br>
<br>
Could you please clarify why you think RFC is wrong here and you<br>
need Content-Type in 304 response?<br></blockquote><div>it is for a facebook app, and i do not have control over this. without this header the css file is not processed as css at all.<br></div></div>