Bug in handling CONNECT requests

[ptlomholt]

There appears to be a bug in handling http CONNECT requests. In a CONNECT request, the uri that follows is of the form hostname:port, but the parser assumes if the first character is not '/', that the uri contains a 'full' uri, including schema, which is not the case for such requests. As a result, parsing fails for such requests.

[ry]

Can you please provide a dump of such a request?

[ptlomholt]

A sample request from http://muffin.doit.org/docs/rfc/tunneling_ssl.html:

CONNECT home.netscape.com:443 HTTP/1.0
User-agent: Mozilla/1.1N
Proxy-authorization: basic aGVsbG86d29ybGQ=

I can get a dump, but from the sample it is pretty obvious what the problem is...

The parser fails when it encounters the first period in the hostname as it assumes it is parsing the schema, not the hostname!
I guess an easy fix would be to skip directly to s_req_host state instead of s_req_schema iff the request is a CONNECT...

[ry]

Fixed in 4cf39fd.