[
https://issues.apache.org/jira/browse/ARTEMIS-2847?focusedWorklogId=461718&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-461718
]
ASF GitHub Bot logged work on ARTEMIS-2847:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 21/Jul/20 19:13
Start Date: 21/Jul/20 19:13
Worklog Time Spent: 10m
Work Description: swerner0 commented on pull request #3221:
URL: https://github.com/apache/activemq-artemis/pull/3221#issuecomment-662054350
ok, thanks. lemme know if you need anything else
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 461718)
Time Spent: 1h 20m (was: 1h 10m)
> socks5h support
> ---------------
>
> Key: ARTEMIS-2847
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2847
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Reporter: Scott Werner
> Priority: Minor
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> SOCKS5 protocol allows for either resolved addresses or domain names. In
> socks5h mode, the proxy performs the name resolution. Netty supports both,
> but Artemis is resolving the IP address before sending to the proxy handler.
> cURL supports the socks5h:// prefix, I suggest introducing a new transport
> parameter, ex. 'socksRemoteDNS', in the broker url which will delay the name
> resolution.
> A user trying to simulate socks5h://host:port using Artemis can then append
> to their url:
> socksEnabled=true&socksHost=<host>&socksPort=<port>&socksRemoteDNS=true
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
