[
https://issues.apache.org/jira/browse/HTTPCLIENT-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12551812
]
Roland Weber commented on HTTPCLIENT-711:
-----------------------------------------
Hi Oleg,
the idea is to have all route computations done in the route planner. If a
specific proxy or local address is needed, then the route planner should know
about it, not the application. A specific route planner can get proxy and local
address data from context (default or request specific), from parameters
(default or request specific), as constructor arguments, or from any other
place like system properties.
I consider the case where the route is computed by the application rather than
in the route planner as rare. Usually, applications should be able to
encapsulate routing logic into a route planner, either the default one or a
custom one. For the rare case that individual requests must be route by the
application explicitly, I was planning to extend the default route planner with
an additional request property or context attribute, see HTTPCLIENT-716.
cheers,
Roland
> bad route computed for redirected requests
> ------------------------------------------
>
> Key: HTTPCLIENT-711
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-711
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Affects Versions: 4.0 Alpha 2
> Reporter: Oleg Kalnichevski
> Priority: Critical
> Fix For: 4.0 Alpha 3
>
>
> BasicRouteDirector appears to miscalculate complex routes. Example to follow.
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
