Re: [quicwg/base-drafts] Introduce HTTP_REQUEST_REJECTED (#2325)

[Mike Bishop <[e-mail]>]

MikeBishop commented on this pull request.



> @@ -963,20 +963,20 @@ for each header field.
 
 ### Request Cancellation
 
-Either client or server can cancel requests by aborting the stream (QUIC
-RESET_STREAM and/or STOP_SENDING frames, as appropriate) with an error code of
+Clients can cancel requests by aborting the stream (QUIC RESET_STREAM and/or
+STOP_SENDING frames, as appropriate) with an error code of
 HTTP_REQUEST_CANCELLED ({{http-error-codes}}).  When the client cancels a
 response, it indicates that this response is no longer of interest.
 Implementations SHOULD cancel requests by aborting both directions of a stream.

>From `-transport`:
> An endpoint SHOULD copy the error code from the STOP_SENDING frame, but MAY use any application error code.

_CANCELLED would be the default behavior; this text merely says that _REJECTED is also acceptable.  (And the transport draft says that the server MAY use any error code, so this is really just a restatement.)

The subtle difference would be an indication of whether the cancelled request had begun to process (and therefore might have had side-effects) before the cancellation took place.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/2325#discussion_r246860205