CONNECT

[martinthomson]

It turns out that CONNECT doesn't map well to the protocol semantics we've developed.

Tatsuhiro Tsujikawa:

For example, CONNECT to remote example.org:443 via
proxy, chrome sends the followings:

:method => CONNECT
:host => example.org
:path => example:org:443
:version => HTTP/1.1

:version is not omitted in HTTP/2.0, so it can be ignored.

This changes the rules for processing :path. Maybe there is a better option than this. We need to consider how to provide CONNECT-equivalent behaviour for explicit proxies.