- From: Austin Wright <aaa@bzfx.net>
- Date: Wed, 4 Nov 2020 18:53:49 -0700
- To: Carsten Bormann <cabo@tzi.org>
- Cc: Sawood Alam <ibnesayeed@gmail.com>, ietf-http-wg <ietf-http-wg@w3.org>
> On Nov 4, 2020, at 15:30, Carsten Bormann <cabo@tzi.org> wrote: > > On 2020-11-04, at 21:49, Austin Wright <aaa@bzfx.net> wrote: >> >> A 204 is identical to sending a 200 response with Content-Length: 0 > > ? > > https://tools.ietf.org/html/rfc7231#section-6.3.5 > > And it’s not like the spec is confabulating here: > > https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/204 > > Grüße, Carsten > What’s the question, exactly? Maybe I’m being unclear. In responses without a Content-Length or Transfer-Encoding header, normally the response message only ends when the TCP connection is terminated. The exception is a 204; the next response begins immediately when the headers end. Cheers, Austin.
Received on Thursday, 5 November 2020 01:54:05 UTC