On Sun, 10 Feb 2002, Ryan Bloom wrote:
> I agree 100% with everything Justin said. The only bug in the code is > that we have a default in the standard config file that doesn't match > the default in the code. My boss keeps trying to convince me that it > is a bug if the software doesn't "just work" with an empty config > file. While I'm not sure I am at that point, I do believe that it is a > bug if we have a default in the standard config that isn't a default > in the code itself. Ryan I meant to comment on this point too. The reason that the default for ForceLanguagePriority is "none" is that this gives the behavior closest to 1.3 and closest to the intentions of the HTTP/1.1 spec. (Although on the latter front, I'm not too sure.) I agree that it is confusing when the default config differs from the server default, but this is far from the only case for that. On the other hand, I won't object if you want to change the default. However, I still believe (strongly) that the behavior with "ForceLanguagePriority none" is wrong in the case of no Accept-Language and should be fixed. Joshua.
