Author martin.panter
Recipients Garfield222, Lukasa, Pierre.Tardy, adambrenecki, berker.peksag, christian.heimes, demian.brecht, icordasc, jitterman, lonetwin, martin.panter, orsenthil, pitrou, r.david.murray, raymondr, serhiy.storchaka, stamparm
Date 2015-09-02.01:27:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1441157227.51.0.0443771118873.issue17849@psf.upfronthosting.co.za>
In-reply-to
Content
Left some review comments. But I don’t completely understand the test case. Is it true there are proxies that do not send a HTTP status line (like HTTP/1.0 200 Connection Established), but do sned the rest of the HTTP header section? This is what the test case seems to be modelling:

Client to proxy request:
b"CONNECT foo:80 HTTP/1.0\r\n"
b"\r\n"

Proxy (plus tunnelled?) response, minus a status line:
b"X-Foo: bar\r\n"
b"\r\n"
b"hello world"

It seems more likely that the proxies related to this bug are misbehaving, or there is some other network problem. Of the proxies mentioned in this report that are accessible to me, both of them do not appear to accept CONNECT requests at all. As soon as the first CONNECT line is send, a HTML blob saying “400 Bad Request” is received, without any HTTP header at all.
History
Date User Action Args
2015-09-02 01:27:07martin.pantersetrecipients: + martin.panter, orsenthil, pitrou, christian.heimes, r.david.murray, berker.peksag, serhiy.storchaka, stamparm, icordasc, demian.brecht, adambrenecki, raymondr, Lukasa, lonetwin, Pierre.Tardy, jitterman, Garfield222
2015-09-02 01:27:07martin.pantersetmessageid: <1441157227.51.0.0443771118873.issue17849@psf.upfronthosting.co.za>
2015-09-02 01:27:07martin.panterlinkissue17849 messages
2015-09-02 01:27:06martin.pantercreate