[
https://issues.apache.org/jira/browse/HTTPCORE-482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory updated HTTPCORE-482:
--
Summary: org.apache.http.nio.protocol.HttpAsyncService returns an empty
response when a
[
https://issues.apache.org/jira/browse/HTTPCORE-482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16129570#comment-16129570
]
ASF subversion and git services commented on HTTPCORE-482:
--
Commit
[
https://issues.apache.org/jira/browse/HTTPCORE-482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory updated HTTPCORE-482:
--
Description:
org.apache.http.nio.protocol.HttpAsyncService does returns an empty response
[
https://issues.apache.org/jira/browse/HTTPCORE-482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory updated HTTPCORE-482:
--
Attachment: httpcomponents-core-4.4.x.patch
> org.apache.http.nio.protocol.HttpAsyncService
Oleg,
I created a ticket and a branch for
https://issues.apache.org/jira/browse/HTTPCORE-482
Can you please review/update and merge if OK?
Thank you,
Gary
On Wed, Aug 16, 2017 at 3:00 PM, Gary Gregory
wrote:
> Hi All (Oleg, really)
>
> I am wondering how to fix/deal
[
https://issues.apache.org/jira/browse/HTTPCORE-482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory updated HTTPCORE-482:
--
Description:
org.apache.http.nio.protocol.HttpAsyncService does returns an empty response
[
https://issues.apache.org/jira/browse/HTTPCORE-482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory updated HTTPCORE-482:
--
Description:
org.apache.http.nio.protocol.HttpAsyncService does returns an empty response
Gary Gregory created HTTPCORE-482:
-
Summary: org.apache.http.nio.protocol.HttpAsyncService does
returns an empty response when a socket timeout is detected
Key: HTTPCORE-482
URL:
Hi All (Oleg, really)
I am wondering how to fix/deal with the a timeout occurring in an async
proxy when an origin server takes too long to reply.
You can reproduce this issue with our asyn example NHttpReverseProxy:
Start it with: http://postman-echo.com
Then run:
curl --verbose