[
https://issues.apache.org/jira/browse/GERONIMO-3706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552754
]
Rick McGuire commented on GERONIMO-3706:
----------------------------------------
Should the proxy configuration be specified on the HttpRequestMessage or on the
AsyncHttpClient? There's going to need to be some attribute set on the message
that allows the request encoder to know if the request needs to be a proxy
request or a normal direct request. This could be something that's turned on
by the AsyncHttpClient or the request could directly carry the proxy
information and the AsyncHttpClient could use the information from the request
to determine how to make the connection. This is somewhat similar to how the
SSLContext information is handled.
> 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.
