Bug 51402 - "ForceLanguagePriority Fallback" not working as implied in the documentation
Summary: "ForceLanguagePriority Fallback" not working as implied in the documentation
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_negotiation (show other bugs)
Version: 2.2.17
Hardware: PC Linux
: P2 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
Keywords: MassUpdate
Depends on:
Reported: 2011-06-21 11:33 UTC by Jan Lanik
Modified: 2018-11-07 21:10 UTC (History)
1 user (show)


Note You need to log in before you can comment on or make changes to this bug.
Description Jan Lanik 2011-06-21 11:33:40 UTC
Suppose we have files hello.html.en, hello.html.de and hello.html.fr

The MultiViews option is enabled and the language priority is set as follows:
LanguagePriority en de fr es

Furthermore we have 
ForceLanguagePriority Fallback

Now let start the server and send a request for hello.html with 
Accept-Language: sp; q=0.8, en; q=0.2, de; q=0.2, fr; q=0.2

As ForceLanguagePriority Prefer is not set, we should (according to http://httpd.apache.org/docs/2.2/mod/mod_negotiation.html )
we should get a http status 300 (MULTIPLE CHOICES).

But when I run it actually I got hello.html.fr (!). So not only it does not
conform to the documentation which implies that an error should be returned,
but also intuitively the result is wrong as the logical choice would be english (as it is when Prefer specified).
Comment 1 Jan Lanik 2011-06-21 11:42:24 UTC

If we set
ForceLanguagePriority None

then as a response for the request for hello.html without Accept-Language header 
the french file was returned
Comment 2 William A. Rowe Jr. 2018-11-07 21:10:01 UTC
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd.

As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd.

If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question.

If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with.

Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.