Hlela i-SOCKS5 proxy ye-Qpid JMS ngama-Netty handlers

Xhumanisa umhlinzeki we-SOCKS5 ProxyHandler ngokusebenzisa izandiso zokuxhumana ze-Qpid JMS kuyilapho ugcina i-AMQPS broker URI.

Ukuthutha kwe-Netty kwe-Qpid JMS kungathola isiphathimandla se-proxy esisha ngesandiso sokuxhumana:

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);

I-Supplier ne-InetSocketAddress yizinhlobo ze-JDK. Iziphathimandla ze-proxy zingeze-Netty, kanti ifektri ne-enum yesandiso ngeze-org.apache.qpid.jms.

Kum-broker ofinyeleleka esidlangalaleni emzileni we-proxy womphakathi ovunyelwe, uhlu lwe-proxy lwe-SOCKS5 lunikeza abazongenela i-host ne-port; qinisekisa ukuthi i-node ekhethiwe ivumela i-host ne-port yangempela ye-broker. Isandiso sibuyisela umhlinzeki; ucingo ngalunye lomhlinzeki ludala isiphathimandla esisha. Ukubuyisela isiphathimandla esisodwa esiguqukayo esibanjwe ezixhumanisweni eziningi kuzophula leyo ntela yobunikazi.

Nge-SOCKS5 authentication, sebenzisa i-handler overload eyamukela igama lomsebenzisi nephasiwedi. Gcina imininingwane ye-broker kuxhumano lwe-JMS futhi gcina i-AMQPS broker URI yangempela kanye negama le-TLS.

Isandiso sisekela iziphathimandla ze-proxy ze-HTTP, SOCKS4 ne-SOCKS5 ze-Netty. Kwi-HTTP CONNECT, umxhumanisi kufanele avume i-port okuqondiwe ye-broker.

Izihloko ezihlobene