Benjamin Peterson added the comment:
The spec, https://tools.ietf.org/html/rfc7230#section-2.6, is quite clear that
the HTTP version is case sensitive. In practice, not every client is lax.
Firefox does a case-insensitive comparison, but libcurl requires uppercase.
That makes me think we can
New submission from Álvaro Muñoz :
Recently faced an issue with a proxy responding in lowercase http, which caused
this:
ProtocolError('Connection aborted.', BadStatusLine('http/1.1 200 connection
established\r\n',))
Changing the string to uppercase before checking if it starts with HTTP fixe
