Re: HTTP/3 CONNECT requests, body, and trailers

On Thu, Feb 5, 2026, at 16:09, Alex Rousskov wrote:
> On 2026-02-04 20:39, Martin Thomson wrote:
> > RFC 9114 says:
> > 
> >> The request stream remains open at the end of the request to carry the data to be transferred. A CONNECT request that does not conform to these restrictions is malformed.
> > 
> > -- https://datatracker.ietf.org/doc/html/rfc9114#section-4.4-5
> > 
> > Reading on a little more, it's clear that the request we're talking about isn't a normal "headers, body, trailers" request, but you might be forgiven for starting to think otherwise.
> > 
> > Would it be worth an editorial erratum? I'd suggest the addition:
> 
> >> A CONNECT request consists of a header block only, it cannot
> >> contain a body; similarly a CONNECT response consists of a header
> >> block only. [...]
> 
> A CONNECT response other than 2xx may include a body, right? For 
> example, a proxy may explain why it denied a particular CONNECT request.

Alex beat me to what I was going to say here. The proposed text could be wordsmithed more I guess. Still not convinced this is a huge spec problem though (the protocol-level requirements are correct IMO, just maybe not super obvious on first inspection but what is?)

Cheers
Lucas
>