Skip to content

Commit

Permalink
Script updating gh-pages from 6fd1a1e. [ci skip]
Browse files Browse the repository at this point in the history
  • Loading branch information
ID Bot committed Oct 14, 2019
1 parent 1e2dfc9 commit e26ca4d
Show file tree
Hide file tree
Showing 3 changed files with 1,411 additions and 1,411 deletions.
4 changes: 2 additions & 2 deletions http/cancel_push_edges/draft-ietf-quic-http.html
Expand Up @@ -1096,8 +1096,8 @@ <h3 id="rfc.section.7.2.3">
<a href="#rfc.section.7.2.3">7.2.3.</a> <a href="#frame-cancel-push" id="frame-cancel-push">CANCEL_PUSH</a>
</h3>
<p id="rfc.section.7.2.3.p.1">The CANCEL_PUSH frame (type=0x3) is used to request cancellation of a server push prior to the push stream being received. The CANCEL_PUSH frame identifies a server push by Push ID (see <a href="#frame-push-promise" class="xref">Section 7.2.5</a>), encoded as a variable-length integer.</p>
<p id="rfc.section.7.2.3.p.2">When a client sends this frame, it is indicating that it does not wish to receive the promised resource. The server SHOULD abort sending the resource, but the mechanism to do so depends on the state of the corresponding push stream. If the server has not yet created a push stream, it does not create one. If the push stream is open, the server SHOULD abruptly terminate that stream. If the push stream has already closed, the server MAY abruptly terminate the stream (cancelling any retransmissions) or MAY take no action.</p>
<p id="rfc.section.7.2.3.p.3">When a server sends this frame, it is indicating that it will not be fulfilling a promise and has not created a push stream. The client should not expect the corresponding promise to be fulfilled.</p>
<p id="rfc.section.7.2.3.p.2">When a client sends CANCEL_PUSH, it is indicating that it does not wish to receive the promised resource. The server SHOULD abort sending the resource, but the mechanism to do so depends on the state of the corresponding push stream. If the server has not yet created a push stream, it does not create one. If the push stream is open, the server SHOULD abruptly terminate that stream. If the server has already fulfilled the promise, the server MAY still abruptly terminate the stream or MAY take no action.</p>
<p id="rfc.section.7.2.3.p.3">When a server sends CANCEL_PUSH, it is indicating that it will not be fulfilling a promise and has not created a push stream. The client should not expect the corresponding promise to be fulfilled.</p>
<p id="rfc.section.7.2.3.p.4">Sending CANCEL_PUSH has no direct effect on the state of existing push streams. A server SHOULD NOT send a CANCEL_PUSH when it has already created a corresponding push stream, and a client SHOULD NOT send a CANCEL_PUSH when it has already received a corresponding push stream.</p>
<p id="rfc.section.7.2.3.p.5">A CANCEL_PUSH frame is sent on the control stream. Receiving a CANCEL_PUSH frame on a stream other than the control stream MUST be treated as a connection error of type HTTP_FRAME_UNEXPECTED.</p>
<div id="rfc.figure.6"></div>
Expand Down
10 changes: 5 additions & 5 deletions http/cancel_push_edges/draft-ietf-quic-http.txt
Expand Up @@ -1435,16 +1435,16 @@ Internet-Draft HTTP/3 October 2019
frame identifies a server push by Push ID (see Section 7.2.5),
encoded as a variable-length integer.

When a client sends this frame, it is indicating that it does not
When a client sends CANCEL_PUSH, it is indicating that it does not
wish to receive the promised resource. The server SHOULD abort
sending the resource, but the mechanism to do so depends on the state
of the corresponding push stream. If the server has not yet created
a push stream, it does not create one. If the push stream is open,
the server SHOULD abruptly terminate that stream. If the push stream
has already closed, the server MAY abruptly terminate the stream
(cancelling any retransmissions) or MAY take no action.
the server SHOULD abruptly terminate that stream. If the server has
already fulfilled the promise, the server MAY still abruptly
terminate the stream or MAY take no action.

When a server sends this frame, it is indicating that it will not be
When a server sends CANCEL_PUSH, it is indicating that it will not be
fulfilling a promise and has not created a push stream. The client
should not expect the corresponding promise to be fulfilled.

Expand Down

0 comments on commit e26ca4d

Please sign in to comment.