[
https://issues.apache.org/jira/browse/GERONIMO-3872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sangjin Lee updated GERONIMO-3872:
----------------------------------
Attachment: GERONIMO-3872.patch
a suggested fix
> proxy connect for https tunneling times out
> -------------------------------------------
>
> Key: GERONIMO-3872
> URL: https://issues.apache.org/jira/browse/GERONIMO-3872
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: AsyncHttpClient
> Affects Versions: 1.x
> Reporter: Sangjin Lee
> Assignee: Rick McGuire
> Attachments: GERONIMO-3872.patch
>
>
> Proxy connect requests (for handling SSL tunneling) are timing out. This is
> a bug introduced when we started handling terminating response message bodies
> when servers close connections.
> Responses to proxy connect requests are 200 responses, but they often do not
> have any headers including Content-Length. The following is one example of
> such a response:
> HTTP/1.1 200 Connection established\r\n
> \r\n
> But the server keeps the connection alive for SSL tunneling. If
> Content-Length is not specified, the response decoder will keep trying to
> read the response until the connection is closed, which will not happen in
> this case. Eventually the connection will time out and the connect handshake
> ends up failing.
> The response decoder needs to be smarter about cases where no content is
> expected. Such cases include
> - certain response status codes (204 and 304)
> - Content-Length: 0 explicitly specified
> - proxy connect responses
> In these cases, the response decoder should recognize it and finish decoding
> immediately.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
