[ 
https://issues.apache.org/jira/browse/HTTPCORE-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885939#comment-17885939
 ] 

ASF subversion and git services commented on HTTPCORE-769:
----------------------------------------------------------

Commit 5e5eb0bde9b991bae9568d39996224cd41041d0b in httpcomponents-core's branch 
refs/heads/master from Arturo Bernal
[ https://gitbox.apache.org/repos/asf?p=httpcomponents-core.git;h=5e5eb0bde ]

HTTPCORE-769 - Add configurable behavior for handling 408 responses in 
DefaultConnectionReuseStrategy. (#489)

This change addresses scenarios where a server sends a 408 response without the 
"Connection: close" header, allowing clients to choose whether to close the 
connection as per RFC recommendations.

> Force close on connection when 408 is returned
> ----------------------------------------------
>
>                 Key: HTTPCORE-769
>                 URL: https://issues.apache.org/jira/browse/HTTPCORE-769
>             Project: HttpComponents HttpCore
>          Issue Type: Bug
>          Components: HttpCore
>    Affects Versions: 5.2.5, 5.3-beta1
>            Reporter: Patrick Barry
>            Priority: Minor
>              Labels: volunteers-wanted
>             Fix For: 5.4-alpha1
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Regarding http1.1 requests.... We have a service we are reaching out to, that 
> is sending back a 408, but no connection: close.  
> According to [https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/408]
>  
> {noformat}
> The HTTP 408 Request Timeout client error response status code indicates that 
> the server would like to shut down this unused connection. A 408 is sent on 
> an idle connection by some servers, even without any previous request by the 
> client.
> A server should send the Connection: close header field in the response, 
> since 408 implies that the server has decided to close the connection rather 
> than continue waiting.
> {noformat}
>  
> We are using the CloseableHttpAsyncClient with 
> PoolingAsyncClientConnectionManager.  When we get a 408 and they do not 
> specify that connection should be closed, how can we force this? Can it be 
> accomplished with an interceptor or is it done by default inside the library? 
>  The response is actually sending back Connection=keep-alive
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
For additional commands, e-mail: dev-h...@hc.apache.org

Reply via email to