[
https://issues.apache.org/jira/browse/GERONIMO-3706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12553283
]
Rick McGuire commented on GERONIMO-3706:
----------------------------------------
I was thinking along the same lines as you. I also believe that is the natural
solution given the mina architecture. Swapping out one filter for the other
seems like it's the correct thing to do, since the characteristics of the
stream change once the connect operator is finished. It also means the
upstream client need not be aware that anything other than a simple socket
connection is taking place.
I have one question about the tunneling. Am I correct in assuming that when
SSL tunneling is being used, that the posted HTTP requests are normal request
messages rather than the full URL messages used when direct proxy
communications are used?
> support for proxy
> -----------------
>
> Key: GERONIMO-3706
> URL: https://issues.apache.org/jira/browse/GERONIMO-3706
> Project: Geronimo
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: AsyncHttpClient
> Affects Versions: 1.x
> Reporter: Sangjin Lee
>
> Proxy support is a critical feature for HTTP clients. I'd like to have
> AsyncHttpClient support proxy. The following would be considered as the
> basic features:
> - Enabling connecting through proxies for http and https targets
> - Exclusion (domains that should not go through proxies)
> - Allowing proxy related configuration on AsyncHttpClient
> - Support for proxy authentication, at least for Basic authentication (and
> perhaps Digest too?)
> There are things like SOCKS support, etc., but the above will be a good
> start. Thoughts?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
