34710 - RFE: Need to make an exclude-list for servers which do wrong things with http/1.1 downloadable

Status: RESOLVED WONTFIX

(Core :: Networking: HTTP, enhancement, P5)

Description

[ruslan]

Need to add some exclude-list for servers which do wrong things with http/1.1.

Comment 1

[Warren Harris]

Moving to M17 which is now considered part of beta2.

Comment 2

[ruslan]

Done. We may want in the future to make such a list downloadable from the 
server. Downgrading the priority for now.

Comment 3

[Henri Sivonen (:hsivonen)]

Could doing things wrong with HTTP 1.1 be autodetected somehow? That is, could
Mozilla generate a list of servers that have done things wrong with HTTP 1.1 by
itself for exclusion in the future?

Comment 4

[Gagan]

pulling in ruslan's necko bugs ->darin

Comment 5

[Gagan]

http bugs to "Networking::HTTP"

Comment 6

[Darin Fisher]

auto-generating exclusion lists would be difficult, b/c error conditions can be
difficult to detect.

Comment 7

[Darin Fisher]

removing dependency on bug 65092 - this bug does not inhibit mozilla's
compliance with HTTP/1.1.

Comment 8

[Michael T. Babcock]

1) Design the format for this list (xml?)
   - consider bad HTTP 1.1, pipelining, SSL, TLS, etc. for future ...
2) Add the code to download such a list
3) Add the preference options to:
   a) download the list ([now] / at startup [x])
   b) specify a URI for the list [http://www.mozilla.org/incompatibleservers.xml]
   c) use the downloaded list [x] <- checkbox
4) Actually start work on the list in CVS ...

Comment 9

[Darin Fisher]

michael: that plan sounds a bit over-engineered to me.  what's wrong w/ a
hard-coded list of bad "Server:" identities as we currently have?  besides,
transparent proxies / virtual hosting proxies tend to break any kind of Server
filtering.

Comment 10

[Matthias Versen [:Matti]]

Http/1.1 is common and the only exception is Pipelining.
We have a fixed blacklist in the code.
Is this still needed now ?