https://issues.apache.org/bugzilla/show_bug.cgi?id=55443
Christoph Anton Mitterer <cales...@scientia.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
--- Comment #2 from Christoph Anton Mitterer <cales...@scientia.net> ---
Hey Eric...
Well...
1) We definitely have some documentation problem as
https://httpd.apache.org/docs/current/mod/mod_negotiation.html#forcelanguagepriority
implies 300 would be sent if it is set to None...
But actually, what I just found out,... if it is set to None... it will simply
not use LanguagePriority but rather fall back to the other steps in the Apache
algo (e.g. smalles file, alphabetically first, etc.) if multiple possibilities
remain.
2) The main idea of this request was: implement some flag, that actually makes
Apache give 300's back, if there are multiple choices... i.e. not following the
"Apache algo"...
3) Why breaking the RFC... well I'd simply say the existence of the 300 mutiple
choices status already implies that it should be used for that.
Of course, the reality is that the browsers are broken, e.g. they usually never
send "*" as an accepted language... thus webservers came along with things like
the fallback... and now no one gives up...
So I guess you cannot simply drop the "legacy" behaviour... but regardless of
whether it's a strict RFC breakage or not (respectively whether it "just"
breaks the intentions of the RFC)... users should at least have the possibility
to get the behaviour that if nothing matches what the client explicitly
specified as Accept, Accept-Language, etc. ... he'll get at 406 (that already
works, well at least for MIME type and language).... and if there are multiple
equal matches, a 300.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org
For additional commands, e-mail: bugs-h...@httpd.apache.org
