Re: Apache's CacheNegotiatedDocs?

I was looking at the Apache documentation last night (for something else
entirely), and it turns out that yes, Apache behaves exactly as
described:

If you fetch one version of a document under (say) content negotiation,
then another version fetched under content negotiation will appear to
have the same last-modified time, regardless of reality. S'just how
Apache does it.

D

Armistead, Jason wrote:
>
> > From: Jan Simek[SMTP:xsimekj@klamm.sh.cvut.cz]
> > Sent: Sunday, 8 March 1998 9:15
> > To: squid-users@nlanr.net
> > Subject: Apache's CacheNegotiatedDocs?
> >
> > Hi,
> >
> > I have a question about Apache's directive CacheNegotiatedDocs. By
> > default it is commented, which means that no documents from given HTTP
> > server should be cached (this is strange, isn't it?). But -- I tried
> > it
> > and our Squid at school caches all my documents (gifs etc., not html)
> > from the server... why?
> >
> Jan
>
> You've answered your own question, but don't yet realise it. The
> directive is for NEGOTIATED documents, that is, documents with a content
> type that is negotiated between the browser and server, such as a server
> that supports multiple languages of the same document URL e.g. Czech and
> English, and can determine what the preferred language encoding is from
> the headers (can't remember what the exact HTTP header is for this) that
> the browser sends with each request. In that case, if you have a file
> welcome.html with Czech and English variants, using the same URL, then
> it naturally can't be cached because an English person would have a hard
> time reading Czech !!!
>
> But, it sounds like your Apache, or at least the files it serves, and
> not enabling such Content Negotiation anyhow, so this is most probably
> why Squid can cache them. You may need to review your Apache
> documentation.
>
> PS: In general, most content-negotiated documents would be HTML, as most
> (but not all) GIF/JPG inline images don't contain language-specific text
> on them.
>
> Regards
>
> Jason

-- 
Did you read the documentation AND the FAQ?
If not, I'll probably still answer your question, but my patience will
be limited, and you take the risk of sarcasm and ridicule.