[
https://issues.apache.org/jira/browse/QPIDJMS-441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16958867#comment-16958867
]
ASF GitHub Bot commented on QPIDJMS-441:
----------------------------------------
stsiano commented on issue #32: QPIDJMS-441: add proxy support
URL: https://github.com/apache/qpid-jms/pull/32#issuecomment-545902790
I have found a workaround for the netty issue with the HTTP Proxy / wss
combination: If we use a HttpRequestEncoder/HttpResponseDecoder combination
instead of the HttpClientCodec, we will have only one of each in the pipeline
and the WebSocketClientHandshaker can add the WebSocketFrameEndcoder/Decoder at
the right place and remove the HttpRequestEncoder/HttoRequestDecoder added by
the NettyWsTransport instead of the HttpClientCodec created by the
HttpProxyHandler.
I prepared that as a second commit (because this actually changes proxy
unrelated coding)
----------------------------------------------------------------
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:
us...@infra.apache.org
> Using QPID JMS behind a proxy
> -----------------------------
>
> Key: QPIDJMS-441
> URL: https://issues.apache.org/jira/browse/QPIDJMS-441
> Project: Qpid JMS
> Issue Type: Wish
> Components: qpid-jms-client
> Affects Versions: 0.40.0
> Reporter: morten
> Priority: Blocker
>
> I actually did not find a possibility to use the jms qpid client behind a
> proxy. I guess there will be a lot of people who needs to run the library
> behind a proxy. It would be nice to have the possibility to set a proxy
> somehow.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
