[ 
https://issues.apache.org/jira/browse/QPIDJMS-441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16960623#comment-16960623
 ] 

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-546702336
 
 
   I have moved the full connection proxy test cases into a separate class.
   
   Furthermore I have reworked the TestProxy class to use nio, so there is no 
explicit thread handling anymore.
   
   I also had a look into the NettySimpleAmqpServer class and its uses 
(NettyTcpToMockServerTest). I did not manage to create a test case with that, 
that succeded with the current code but failed with the HttpClientCodec in the 
NettyWsTransport class, so I kept the activemq tests for the ws connectivity.
 
----------------------------------------------------------------
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]


> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to