[
https://issues.apache.org/jira/browse/HTTPCLIENT-1787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16750285#comment-16750285
]
Roland Schaer commented on HTTPCLIENT-1787:
-------------------------------------------
[~jsedding]
I came across the same issue which seems to exist in OSGiHttpRoutePlanner [1].
While the connection to the target HTTPS URL works, the communication from
client to proxy seems to be HTTP based only, while the proxy establishes a
HTTPS connection to the target URL.
{{Client --[HTTP]--> Proxy --[HTTPS]--> Target}}
I assume a proxy configuration pointing to a proxy which only is reachable
through HTTPS might not work.
https://github.com/apache/httpcomponents-client/blob/4.5.x/httpclient-osgi/src/main/java/org/apache/http/osgi/impl/OSGiHttpRoutePlanner.java#L77
> OSGiHttpRoutePlanner should leverage target scheme while building proxy-ed uri
> ------------------------------------------------------------------------------
>
> Key: HTTPCLIENT-1787
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1787
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: HttpClient (classic)
> Affects Versions: 4.5.2
> Environment: OSGi
> Reporter: Srijan Bhatnagar
> Assignee: Julian Sedding
> Priority: Major
> Labels: stuck, volunteers-wanted
> Fix For: Stuck
>
>
> OSGiHttpRoutePlanner seems to always set the "http" scheme for the proxy-ed
> host instead of figuring it out from the original url.
> It should leverage target scheme while building proxy-ed uri.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
