[EMAIL PROTECTED] Allowing negotiated content to be cached

2006-10-31 Thread Spartanicus
I'm experimenting with multiviews to get more user friendly URLs, and so
that I can change foobar.htm to foobar.cgi without causing problems
or requiring a fix.

Consequently normally the document returned should be the same so I
added CacheNegotiatedDocs On for HTTP/1.0 requests.

What is the best way to allow these types of negotiated documents to
be cached as if they weren't negotiated for HTTP/1.1 requests?

-- 
Spartanicus

(email whitelist in use, non list-server mail will not be seen)

-
The official User-To-User support forum of the Apache HTTP Server Project.
See URL:http://httpd.apache.org/userslist.html for more info.
To unsubscribe, e-mail: [EMAIL PROTECTED]
  from the digest: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [EMAIL PROTECTED] Allowing negotiated content to be cached

2006-10-31 Thread Joshua Slive

On 10/31/06, Spartanicus [EMAIL PROTECTED] wrote:

I'm experimenting with multiviews to get more user friendly URLs, and so
that I can change foobar.htm to foobar.cgi without causing problems
or requiring a fix.

Consequently normally the document returned should be the same so I
added CacheNegotiatedDocs On for HTTP/1.0 requests.

What is the best way to allow these types of negotiated documents to
be cached as if they weren't negotiated for HTTP/1.1 requests?


You need to examine exactly what response headers apache is sending
for these requests and make adjustments as required.  For example, you
might find
SetEnv force-no-vary
or
Header unset Vary
might help.  But I haven't tested that.

Joshua.

-
The official User-To-User support forum of the Apache HTTP Server Project.
See URL:http://httpd.apache.org/userslist.html for more info.
To unsubscribe, e-mail: [EMAIL PROTECTED]
 from the digest: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]