Re: Apache's CacheNegotiatedDocs?

On Sat, 14 Mar 1998, Dancer wrote:

> Henrik Nordstrom wrote:
> >
> > Dancer wrote:
> > > 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.
> >
> > I assume that Apache sends Vary: headers when doing content-negotiation
> > (it should, at least when there is more than possible object for the
> > URL)?
>
> Apparently not. This was from the Apache FAQ.

Erm... no. Please provide an exact citation for that in the FAQ since I'm
sure not aware of it being there.

Apache does send Vary: headers.

The only thing that CacheNegotiatedDocs does is not set an expires header
to indicate it expires right now. This is really obsolete with HTTP/1.1
support and with 1.0 proxies that support more headers than the base 1.0
spec includes.

Example header w/o CacheNegotiatedDocs:

HTTP/1.1 200 OK
Date: Mon, 16 Mar 1998 05:31:09 GMT
Server: Apache/1.3b6-dev
Vary: accept-language
Last-Modified: Mon, 16 Mar 1998 05:30:49 GMT
ETag: "188d1-3-350cb909"
Content-Length: 3
Accept-Ranges: bytes
Connection: close
Content-Type: text/html
Content-Language: en
Expires: Mon, 16 Mar 1998 05:31:09 GMT

and with:

HTTP/1.1 200 OK
Date: Mon, 16 Mar 1998 05:33:45 GMT
Server: Apache/1.3b6-dev
Vary: accept-language
Last-Modified: Mon, 16 Mar 1998 05:30:49 GMT
ETag: "188d1-3-350cb909"
Content-Length: 3
Accept-Ranges: bytes
Connection: close
Content-Type: text/html
Content-Language: en

(this is a request for foo.html with foo.html.en and foo.html.fr
available)
Received on Sun Mar 15 1998 - 21:40:42 MST