Saita proxy na SOCKS5 don Qpid JMS tare da masu sarrafa Netty

Jigilar Netty na Qpid JMS na iya samun sabon mai sarrafa proxy ta hanyar haɓɓaka haɗi:

Supplier<ProxyHandler> handlers = () ->
    new Socks5ProxyHandler(
        new InetSocketAddress("proxy.example", 1080));

JmsConnectionFactory factory = new JmsConnectionFactory(
    "amqps://broker.example:5671");
factory.setExtension(
    JmsConnectionExtensions.PROXY_HANDLER_SUPPLIER.toString(),
    (connection, remote) -> handlers);

Supplier da InetSocketAddress nau'ikan JDK ne. Masu sarrafa proxy na Netty ne, kuma masana'anta da enum na haɓɓaka na org.apache.qpid.jms ne.

Don broker da ake iya isa ga jama'a a kan hanyar proxy ta jama'a da aka yarda, jerin proxy na SOCKS5 yana ba da 'yan takarar host da tashar jiragen ruwa; tabbatar cewa ƙullin da aka zaɓa yana ba da izinin ainihin host da tashar jiragen ruwa na broker. Haɓɓakar tana mayar da mai samarwa; kowace kira ta mai samarwa tana ƙirƙirar sabon mai sarrafa. Mayar da mai sarrafa guda ɗaya da aka kama don haɗi da yawa zai keta wannan tsarin mallaka.

Don tabbatarwar SOCKS5, yi amfani da ƙarin nauyin mai sarrafa da ke karɓar sunan mai amfani da kalmar sirri. Riƙe takaddun shaidar broker a kan haɗin JMS kuma ka riƙe ainihin URI na broker AMQPS da sunan TLS.

Haɓɓakar tana tallafawa masu sarrafa proxy na HTTP, SOCKS4 da SOCKS5 na Netty. Don HTTP CONNECT, matsakaici dole ne ya ba da izinin tashar manufa ta broker.