Re: [quicwg/base-drafts] http deadlock with stream FIN choices (#1972)

[Kazuho Oku <[e-mail]>]

Re HQ, I think we have a clear definition. [Section 5.1](
https://quicwg.org/base-drafts/draft-ietf-quic-http.html#rfc.section.5.1) states that:
> An HTTP request/response exchange fully consumes a bidirectional QUIC stream. After sending a request, a client closes the stream for sending; after sending a final response, the server closes the stream for sending and the QUIC stream is fully closed. Requests and responses are considered complete when the corresponding QUIC stream is closed in the appropriate direction.

I would interpret this statement that it is OK to use FIN as the way to determine the end of a HTTP request.

FWIW, this follows what we have had for H2 in [RFC 7540 section 8.1](
https://httpwg.org/specs/rfc7540.html#rfc.section.8.1)

Re CONNECT case that @LPardue points out, my understanding is that is considered either as an exception or that CONNECT elicits an early response.

-- 
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/1972#issuecomment-436448098