-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document how to support proxying via web sockets #40
Comments
We should also include a note around the proxy needing to support websockets to work with this method. |
Hi, we encountered the same issue and it cost us lot of time to find this solution. When do you think it will be documented? Thanks. |
Dear, I try to use the not founded in this issue, but it does not work if proxy requires authentication. I tried to add
But it does not work, do you have some advices ? Thx |
Maybe swithcing libraries is worthwhile? https://techcommunity.microsoft.com/t5/messaging-on-azure-blog/azure-event-hubs-websockets-and-proxy-support/ba-p/371136 |
This plugin supports using a proxy, but setting it up is currently tricky - it requires the proxy to have web socket support and the settings are not intuitive to do so. Until we have proper support for proxying, we should document the steps (and prerequisites) to support proxying. Much of the detail is in #29, but should be added more formally.
Posted the actual thing to be documented to ensure it raises visibility:
Add an environment variable that contains the proxy
export https_proxy="https://my_proxy:8080"
Add the following to the connection String
;TransportType=AmqpWebSockets
(A user followed up to the issue and stated that adding these to
jvm.options
may be necessary)
The text was updated successfully, but these errors were encountered: