[quicwg/base-drafts] Error code for indicating that a HTTP response is aborted (#2416)

[Kazuho Oku <[e-mail]>]

When a reverse proxy forwards a HTTP response to the client, sometimes it sees the upstream server terminate the response early. For example, a HTTP/1.1 connection being closed prior to transmitting number of bytes specified by the `content-length` field. Or a chunked response being closed abruptly.

The only way of delegating such a condition to the client in HTTP/2 was to send a RST_STREAM frame with `PROTOCOL_ERROR`. However, use of the error code is awkward in this case, considering the fact that the error did not happen within the communication between the endpoints using the particular HTTP/2 connection.

I think it makes sense to have an error code that better designates the case.

One way to address the issue in H3 would be to change `HTTP_REQUEST_CANCELLED` to `HTTP_MESSAGE_CANCELLED`, and let the server use the error code (as an argument of the RESET_STREAM frame) to indicate that the response has been "cancelled".

Originally proposed in 
https://github.com/quicwg/base-drafts/issues/2410#issuecomment-460330192.

-- 
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/issues/2416