hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roland Weber (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (HTTPCLIENT-334) Per socket SOCKS proxies
Date Sat, 01 Sep 2007 15:57:19 GMT

     [ https://issues.apache.org/jira/browse/HTTPCLIENT-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Roland Weber resolved HTTPCLIENT-334.

    Resolution: Fixed

ClientConnectionOperator.openConnection has access to HttpParams and HttpContext.
I think that's enough to address this requirement by plugging in a custom CCO.

HttpRoute does not make provisions for representing socks proxies. They could be inserted
into the route as a proxy with socks: protocol, to make the connection manager socks-aware.
That would throw off a lot of the upper layers though.
Another way to represent the socks proxy in the route would be as the "local address". That
should not cause problems in the upper layers, you just can't combine socks proxies and actual
local addresses that way.


> Per socket SOCKS proxies
> ------------------------
>                 Key: HTTPCLIENT-334
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-334
>             Project: HttpComponents HttpClient
>          Issue Type: Improvement
>          Components: HttpConn
>    Affects Versions: Snapshot
>         Environment: Operating System: All
> Platform: All
>            Reporter: Sam Berlin
>            Priority: Minor
>             Fix For: 4.0 Alpha 2
>         Attachments: changes.txt
> HttpClient requires a way of allowing a SOCKS proxy to be used on some
> connections without requiring that all created Sockets go through the proxy.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail: httpcomponents-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpcomponents-dev-help@jakarta.apache.org

View raw message