Re: Ambiguity on HTTP/3 HEADERS and QUIC STREAM FIN requirement

On Fri, Jun 17, 2022 at 10:31:39AM -0700, David Schinazi wrote:
> Since it's Friday and we're exploring crazy thoughts, instead of
> ":no-content" why not simply content-length=0?

You're right that it already exists for exactly that purpose and
would work out of the box. And any intermediary will be free to
drop it when converting to H1 for methods that do not use a body
by default, and it could be used as a work-around for those that
for various reasons cannot send the FIN bit.

Then I would suggest that we'd recommend that senders emit the FIN
(or ES in H2 but that's already the case) along with the HEADERS
frame, and that if they're not able to do it, as an alternative
they should explicitly send content-length:0 to inform the recipient
that it must not expect anything else.

I'm pretty sure that we can come up with such a reasonable solution
that can end up as an implementation advice so that we don't put any
implementation into a difficult situation, so let's continue down
that route!


Received on Friday, 17 June 2022 17:47:05 UTC