DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23798>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23798 Mention force-no-vary workaround in Content Negotiation docs Summary: Mention force-no-vary workaround in Content Negotiation docs Product: Apache httpd-2.0 Version: HEAD Platform: All OS/Version: All Status: NEW Severity: Enhancement Priority: Other Component: Documentation AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] Some or all versions of Internet Explorer seems to not cache a resources with *any* Vary header. See discussion: http://marc.theaimsgroup.com/?l=apache-httpd-users&m=106579308905249&w=2 The environment variable "forve-no-vary" can be used as a workaround, and this is mentioned in the document Environment Variables. This should be pointed out in the Content Negotiation document, under the section "Note on Caching", as well, with a pointer to the env doc. I'm no good with authoring ;), but something like this could be added to http://httpd.apache.org/docs-2.0/content-negotiation.html#caching : "Some clients don't interpret the Vary header, set in negotiated responses, correctly (see the known client problems page <./misc/known_client_problems.html>). This can result in that resources are not properly cached. Setting the special force-no-vary environment variable may help (see Special Purpose Environment Variables <./env.html#special>). Example: BrowserMatch MSIE force-no-vary=1 " This is, of course, also relevant to Apache 1.3. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
