After fix for bug 109553 was committed, one major server failed because of HTTP content-location badly configured: bug 231072.
After 1.7b was released, it seems like this rate is increasing: bug 238156, bug 238314.
The worrying part is that 10% of the IIS servers seem to be wrongly configured on the Internet (not to mention the Intranet servers), according to:
http://www.securityspace.com/s_survey/data/man.200402/firewalled_cloc.html
[...]
Number of IIS Servers that revealed an IP in the Content-Location tag different from the IP accepting the connection 75,938 9.40%
[...]
1.7 will to be the first non-beta release of Mozilla (Firefox 0.8 doesn't have it) to ship with this new feature and I'm afraid it could fail on many servers.
I wanted to discuss this to avoid filing a bug report, possible solutions:
- a pref to disable it ? by default ?
- not taking care of content-location when served by IIS and Oracle9 (the servers we've seen so far) ?
Don't take me wrong, it's appreciable to have this but so many servers seem to be wrongly configured it could hurt Mozilla (bad publicity, not compatible with servers, etc.)
Mozilla has done something similar with HTTP pipelining in the past: http://lxr.mozilla.org/seamonkey/source/netwerk/protocol/http/src/nsHttpConnection.cpp#236
Rgds, Olivier _______________________________________________ Mozilla-netlib mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-netlib
