From: Joshua Slive Date: Wed, 23 Jul 2003 22:39:24 +0000 (+0000) Subject: - In 2.0 it is possible for LanguagePriority to have an effect, even for X-Git-Tag: pre_ajp_proxy~1382 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=5060c35c4949c557504f9147d024f924b7932520;p=apache - In 2.0 it is possible for LanguagePriority to have an effect, even for a properly configured HTTP/1.1 client. - Reference MultiViewsMatch. PR: 21726, 21830 git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@100753 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/mod/mod_negotiation.html.en b/docs/manual/mod/mod_negotiation.html.en index d331484f07..61bc7d5ece 100644 --- a/docs/manual/mod/mod_negotiation.html.en +++ b/docs/manual/mod/mod_negotiation.html.en @@ -169,6 +169,11 @@ Negotiation content-encodings it would have if the client had asked for one of them by name. It then chooses the best match to the client's requirements, and returns that document.

+ +

The MultiViewsMatch + directive configures whether Apache will consider files + that do not have content negotiation meta-information assigned + to them when choosing files.

top

CacheNegotiatedDocs Directive

@@ -283,8 +288,8 @@ the client does not express a preference

Note that this directive only has an effect if a 'best' language cannot be determined by any other means or the ForceLanguagePriority directive - is not None. Correctly implemented HTTP/1.1 requests - will mean this directive has no effect.

+ is not None. In general, the client determines the + language preference, not the server.

See also