Re: [quicwg/base-drafts] Rearrange discussion of cancellation and rejection (#3926)

[Mike Bishop <[e-mail]>]

@MikeBishop commented on this pull request.



> -some higher layer of software that might have taken some action as a result. The
-client can treat requests rejected by the server as though they had never been
-sent at all, thereby allowing them to be retried later on a new connection.
-Servers MUST NOT use the H3_REQUEST_REJECTED error code for requests which
-were partially or fully processed.  When a server abandons a response after
-partial processing, it SHOULD abort its response stream with the error code
-H3_REQUEST_CANCELLED.
-
-When a client resets a request with the error code H3_REQUEST_CANCELLED, a
-server MAY abruptly terminate the response using the error code
-H3_REQUEST_REJECTED if no processing was performed.  Clients MUST NOT use the
-H3_REQUEST_REJECTED error code, except when a server has requested closure of
-the request stream with this error code.
-
-If a stream is cancelled after receiving a complete response, the client MAY
+Once a request has been sent, it MAY be cancelled by either endpoint.  Clients

Technically, the stream needn't have any bytes sent.

-- 
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/3926#discussion_r459057618