ContentType - text/css for css files in 304 Not Modified
kevincastiglione at gmail.com
Thu Sep 2 05:02:34 MSD 2010
On Wed, Sep 1, 2010 at 4:39 PM, Maxim Dounin <mdounin at mdounin.ru> wrote:
> On Wed, Sep 01, 2010 at 01:23:38PM -0700, kevin wrote:
> > i want nginx to include ContentType text/css for css files in 304 Not
> > Modified request
> > here is the headers for the static css file request. you can see that
> > is no ContentType sent.
> RFC 2616 says about 304 responses:
> If the conditional GET used a strong cache validator (see section
> 13.3.3), the response SHOULD NOT include other entity-headers.
> Otherwise (i.e., the conditional GET used a weak validator), the
> response MUST NOT include other entity-headers; this prevents
> inconsistencies between cached entity-bodies and updated headers.
> Content-Type is entity header and not listed above this paragraph,
> so clearly qualifies as "other entity-headers".
> Could you please clarify why you think RFC is wrong here and you
> need Content-Type in 304 response?
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.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the nginx