Re: Suspected ambiguity in H1 around Expect: 100-continue

On 8/12/25 16:13, Willy Tarreau wrote:
> Hi Mike!
> 
> On Tue, Aug 12, 2025 at 08:08:25PM +0000, Mike Bishop wrote:
>> Section 7.5 of RFC9110 says:
>> A client that receives a response while it is still sending the associated request SHOULD continue sending that request unless it receives an explicit indication to the contrary (see, e.g., Section 9.5<https://httpwg.org/specs/rfc9112.html#persistent.failures> of [HTTP/1.1]<https://httpwg.org/specs/rfc9110.html#HTTP11> and Section 6.4<https://www.rfc-editor.org/rfc/rfc9113.html#section-6.4> of [HTTP/2]<https://httpwg.org/specs/rfc9110.html#HTTP2>).
>> Section 9.3 of RFC9112 says:
>> A server MUST read the entire request message body or close the connection after sending its response; otherwise, the remaining data on a persistent connection would be misinterpreted as the next request. Likewise, a client MUST read the entire response message body if it intends to reuse the same connection for a subsequent request.
>> Section 9.5 of RFC9112 says:
>> A client sending a message body SHOULD monitor the network connection for an error response while it is transmitting the request. If the client sees a response that indicates the server does not wish to receive the message body and is closing the connection, the client SHOULD immediately cease transmitting the body and close its side of the connection.
>> Servers MUST either eat the entire body or close the connection; if the server has told you it doesn't want the body, the latter implies that a server will probably be closing the connection, but the client SHOULD do so immediately whether the server does or not.
>>
>> I think what's missing is a second sentence in the first quote which says if the client doesn't continue sending the request, it MUST close the connection.
> 
> Yes I agree! Also IMHO it's not very likely that someone implementing
> Expect will immediately jump to that part of the spec. We need to keep
> in mind that it's large nowadays and paragraphs are far apart. I think
> that the part about expect should just add a sentence saying that
> Expect doesn't save the client from uploading a body if it wants to
> keep the connection alive, or it must close the connection if it does
> not (or cannot) send it.

With chunked encoding, can it just send "0\r\n\r\n" regardless of what
it would otherwise have sent?
-- 
Sincerely,
Demi Marie Obenour (she/her/hers)