Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Describe CONNECT method #100

Merged
merged 5 commits into from Jan 12, 2017
Merged

Describe CONNECT method #100

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
43830f3
Describing CONNECT method for #95
MikeBishop Dec 23, 2016
cd6c622
Martin's feedback on CONNECT
MikeBishop Jan 3, 2017
e20c7cd
Addressing feedback
MikeBishop Jan 12, 2017
59cf444
Merge remote-tracking branch 'origin/master' into connect
MikeBishop Jan 12, 2017
e9081f3
Hook up the error code
MikeBishop Jan 12, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
22 changes: 12 additions & 10 deletions draft-ietf-quic-http.md
View file
Open in desktop
Expand Up @@ -248,12 +248,12 @@ do we need to retain compatibility with HTTP/2's HPACK?

### The CONNECT Method

In HTTP/1.x, the pseudo-method CONNECT ({{!RFC7231}}, Section 4.3.6) is used to
convert an HTTP connection into a tunnel to a remote host. CONNECT is primarily
used with HTTP proxies to establish a TLS session with an origin server for the
purposes of interacting with "https" resources. In HTTP/2, the CONNECT method is
used to establish a tunnel over a single HTTP/2 stream to a remote host for
similar purposes.
The pseudo-method CONNECT ({{!RFC7231}}, Section 4.3.6) is primarily used with
HTTP proxies to establish a TLS session with an origin server for the purposes
of interacting with "https" resources. In HTTP/1.x, CONNECT is used to convert
an entire HTTP connection into a tunnel to a remote host. In HTTP/2, the CONNECT
method is used to establish a tunnel over a single HTTP/2 stream to a remote
host for similar purposes.

A CONNECT request in HTTP/QUIC functions in the same manner as in HTTP/2. The
request MUST be formatted as described in {{!RFC7540}}, Section 8.3. A CONNECT
Expand All @@ -272,10 +272,12 @@ proxy to the TCP server; data received from the TCP server is written to the
data stream by the proxy. Note that the size and number of TCP segments is not
guaranteed to map predictably to the size and number of QUIC STREAM frames.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Move this last sentence to the previous paragraph.


The TCP connection can be closed by either peer. When the client half-closes the
data stream, the proxy will set the FIN bit on its connection to the TCP server.
When the proxy receives a packet with the FIN bit set, it will half-close the
corresponding data stream.
The TCP connection can be closed by either peer. When the client half-closes the
data stream, the proxy will set the FIN bit on its connection to the TCP server.
When the proxy receives a packet with the FIN bit set, it will half-close the
corresponding data stream. TCP connections which remain half-closed in a single
direction are not invalid, but are often handled poorly by servers, so clients
SHOULD NOT half-close connections on which they are still expecting data.

A TCP connection error is signaled with RST_STREAM. A proxy treats any error in
the TCP connection, which includes receiving a TCP segment with the RST bit set,
Expand Down