[
https://issues.apache.org/jira/browse/HTTPCORE-740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17725637#comment-17725637
]
Arunan Sugunakumar commented on HTTPCORE-740:
---------------------------------------------
Hi Oleg,
Thanks for your reply. We ran several tests and we did not find any issues with
it. I have made the PR ready for review.
Thanks & Regards,
Arunan
> Connection resets during timeouts
> ---------------------------------
>
> Key: HTTPCORE-740
> URL: https://issues.apache.org/jira/browse/HTTPCORE-740
> Project: HttpComponents HttpCore
> Issue Type: Bug
> Components: HttpCore NIO
> Affects Versions: 4.4.16
> Reporter: Arunan Sugunakumar
> Priority: Major
> Attachments: HttpNIOTestServer-740.zip, Screenshot 2023-04-18 at
> 07.53.12.png, Screenshot 2023-04-18 at 13.43.02.png, Screenshot 2023-04-18 at
> 13.44.01.png, Screenshot 2023-04-18 at 13.45.10.png
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> We observed an issue where with a httpcore-nio server timeout scenario, the
> server sends a FINACK to the client and if the client sends a close_notify
> alert, the server is immediately sending a RESET and closing the connection.
> Ideally, the server should also send a close_notify and terminate the
> connection gracefully. This issue is observed with only the clients which
> send close_notify for a server FINACK. The below attached is a TCP capture
> during the timeout scenario (server port: 8253). The server uses the latest
> 4.4.16 httpcore-nio library.
> !Screenshot 2023-04-18 at 07.53.12.png|width=1466,height=150!
> Is there any way to avoid this scenario and send a close_notify from the
> server as well to terminate the connection gracefully?
> PS: I am currently working on a simple reproducer to attach here, and I'll
> attach it as soon as possible.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
