Fix OneTimeReadTimeoutHandler removed by TLS handshake for 100-contin…

[zoewangg]

…ue requests

Motivation and Context

OneTimeReadTimeoutHandler was added at the front of the pipeline via addFirst, placing it before SslHandler. During the TLS handshake on new connections, raw encrypted bytes arrived as channelRead events and caused the handler to remove itself before the HTTP 100 Continue response could arrive. This left no read timeout handler active, causing requests with Expect: 100-continue to hang indefinitely when no response is received.

Modifications

• Changed OneTimeReadTimeoutHandler pipeline position from addFirst to addBefore(HttpStreamsClientHandler) in NettyRequestExecutor.writeRequest(), so the handler only sees decoded HTTP messages and is not affected by TLS handshake data
• Added Expect100ContinueReadTimeoutTest — an integration test with a slow-handshake TLS server that never responds to 100-continue. The test hangs without the fix and passes with it.

Testing

• Expect100ContinueReadTimeoutTest — verified it fails (hangs) pre-fix and passes post-fix

• Existing tests pass

• Added unit tests

• Ran existing tests

• Manual testing performed

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)

Checklist

• I have read the CONTRIBUTING document
• Local run of mvn clean install -pl :netty-nio-client succeeds
• My code follows the code style of this project
• My change requires a change to the Javadoc documentation
• I have updated the Javadoc documentation accordingly
• I have added tests to cover my changes
• All new and existing tests passed
• I have added a changelog entry
• My change is to implement 1.11 parity feature and I have updated LaunchChangelog

License

• I confirm that this pull request can be released under the Apache 2 license

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud