[
https://issues.apache.org/jira/browse/HTTPCORE-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16558783#comment-16558783
]
Gary Gregory commented on HTTPCORE-544:
---------------------------------------
{quote}I do not know what exactly you are trying to accomplish but In my
opinion socket timeout does not belong to EndpointDetails.
{quote}
The big picture is that our server, which is designed to stay up for a long
time and have all of its guts reconfigurable needs to do a lot of logging and
one of the issues users have sometimes is around timeout issues while, for
example, passing traffic to other origin servers. So for certain log entries,
we need to say "request R to origin server O is en route with a N second
timeout" and "request so and so from client 1.2.3.4 is being processed under a
N second timeout."
So where can I get the current connection's timeout (from a client or to an
origin server) from an HttpRequest and HttpContext, for example, when you
implement
{{org.apache.hc.core5.http.nio.AsyncServerExchangeHandler.handleRequest(HttpRequest,
EntityDetails, ResponseChannel, HttpContext)}}?
Thank you,
Gary
> Add org.apache.hc.core5.http.EndpointDetails.getSocketTimeout()
> ---------------------------------------------------------------
>
> Key: HTTPCORE-544
> URL: https://issues.apache.org/jira/browse/HTTPCORE-544
> Project: HttpComponents HttpCore
> Issue Type: New Feature
> Reporter: Gary Gregory
> Assignee: Gary Gregory
> Priority: Major
> Fix For: 5.0-beta3
>
>
> Add {{org.apache.hc.core5.http.EndpointDetails.getSocketTimeout()}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
