[
https://issues.apache.org/jira/browse/HTTPCORE-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13797798#comment-13797798
]
Oleg Kalnichevski commented on HTTPCORE-356:
--------------------------------------------
Complex connection routing is out of scope for HttpCore. If you need proxy
support, why don't you simply use HttpAsyncClient [1]? HttpAsyncClient package
also provides a more advanced implementation of a non-blocking connection pool
with support for complex connection routes.
Oleg
[1] http://hc.apache.org/httpcomponents-asyncclient-4.0.x/index.html
> Please add support for automatic proxy selection for httpcore-nio
> ------------------------------------------------------------------
>
> Key: HTTPCORE-356
> URL: https://issues.apache.org/jira/browse/HTTPCORE-356
> Project: HttpComponents HttpCore
> Issue Type: Improvement
> Components: HttpCore NIO
> Affects Versions: 4.3
> Reporter: Robert Stupp
>
> I tried to add support for httpcore-nio to our internal libraries, that still
> use synchronous IO.
> We have a central place in our libraries, that provides a "singleton" http
> support with proxy configuration per target host.
> This works fins in httpcore 4.2 using java.net.ProxySelector and
> org.apache.http.impl.conn.ProxySelectorRoutePlanner.
> I digged into the httpcore-nio code and could not find any place where a such
> decisions are made. The HttpHost provided as "route" parameter is passed 1:1
> to NIO connection pool, which is wrong for proxied hosts :(
> I assume that a "proxy capable" implementation of HttpAsyncRequestProducer is
> needed.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
