On Thu, 9 Oct 2025 14:04:58 GMT, Josiah Noel <[email protected]> wrote:
>> Following the guideline of the last comment on >> [JDK-8349670](https://bugs.openjdk.org/browse/JDK-8349670?focusedId=14794649&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14794649), >> resolves the issue where sending a 1xx status code would close the input >> stream, preventing the server from reading the body. >> >> - When a 1xx status code is sent by `sendResponseHeaders`, the input/output >> streams will not be closed prematurely. >> - sentHeaders will not be set to true when sending 1xx status codes >> - 100-continue will be sent automatically when trying to read the >> inputstream if `Expect: 100-continue` header is present > > Josiah Noel has updated the pull request incrementally with two additional > commits since the last revision: > > - Update InputRead100Test.java > - actually fail if sent twice Noted. But https://www.rfc-editor.org/rfc/rfc7231.html#section-6.2 > A client MUST be able to parse one or more 1xx responses received > prior to a final response, even if the client does not expect one. A > user agent MAY ignore unexpected 1xx responses. I don't see anything hinting that 100 should be special in this respect. ------------- PR Comment: https://git.openjdk.org/jdk/pull/27069#issuecomment-3386179239
