|
> For example, if a server did do content negotiation then the Content-Type: header would be different for the different types of responses, depending on the type of content negotiated. In that case the server can add a Vary: content-type header, which causes the cache to consider the Content-Type: header when caching responses from that URI.
This reads as if you think it's the varying *response* header that should be listed in the Vary header, when in actual fact it's the varying *request* header that should be listed. So Vary: Content-Type is almost certainly wrong, you want Vary: Accept if you are doing content negotiation.
http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.44
|