RFR: 8349670: HttpServer: sending interim responses fails after JDK-7026262 [v21]

Josiah Noel duke at openjdk.org
Fri Oct 10 13:25:32 UTC 2025


On Fri, 10 Oct 2025 10:14:03 GMT, Michael McMahon <michaelm at openjdk.org> wrote:

> 103

103 is for http2, and a lot of clients won't even accept it if the connection is not on http2

> If it's the response headers returned from getResponseHeaders then is this map cleared after the intermediate response or is the user supposed to clear it? Does this work?

alright going back to 101 for a second, there is no difficulty, as the 101 _is_ the final response with the final headers, rather than other codes. I can toss this PR and get back exclusively to 101 if we decide the effects for 100-continue are undesirable. 

> If we are supporting 100 Continue now (under user control) does the expected behavior work? If a client sends a request with an Expect: 100-Continue header and waits for the intermediate response before sending the request body, does this actually work?

We removed that behavior from this PR, but while it was in here ([4b00588](https://github.com/openjdk/jdk/pull/27069/commits/4b0058886cf10b1703426acc4131453c46636645#diff-04936de6755028a0d5eb76804c124f811dca641818ef59a2201566d01c3c1441R163-R167)), it worked as expected, the client waited for the manually sent 100 code to send the body and everything.

-------------

PR Comment: https://git.openjdk.org/jdk/pull/27069#issuecomment-3390079283


More information about the net-dev mailing list