[
https://issues.apache.org/jira/browse/AMQ-9102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17638721#comment-17638721
]
ASF subversion and git services commented on AMQ-9102:
------------------------------------------------------
Commit 44a5539afc689f23c63a0d2e1786b48c0e52f3c3 in activemq's branch
refs/heads/main from Jean-Baptiste Onofré
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=44a5539af ]
[AMQ-9102] Add http.nonProxyHost support in HTTP transport
> HTTP Proxy Exclusions are not applied to ActiveMQ Connections
> -------------------------------------------------------------
>
> Key: AMQ-9102
> URL: https://issues.apache.org/jira/browse/AMQ-9102
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.16.3
> Reporter: Stephan Wagner
> Assignee: Jean-Baptiste Onofré
> Priority: Major
> Fix For: 5.18.0, 5.17.3
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> In [this
> commit|https://github.com/apache/activemq/commit/1ced34a383c5e3910c582fd3bfd720a8f6fcde32]
> basic HTTP-Proxy support using the default properties was added to ActiveMQ,
> however the implementation does not account for the [exclusion list in
> property
> "http.nonProxyHosts"|https://docs.oracle.com/javase/8/docs/technotes/guides/net/proxies.html],
> which leads to issues in environments that use a system proxy, but exclude
> certain targets from proxy usage.
> Given the implementation in {{HttpTransportSupport}} (in particular
> {{{}getProxyHost(){}}}) and {{HttpClientTransport}} (in particular creation
> of the HTTP Client) there is no way to use ActiveMQ in a mixed
> non-proxy/proxy environment.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
