SOCKS don toshe hanyoyin haɗin RabbitMQ marasa TLS a cikin Spring AMQP

Don haɗin AMQP mai toshewa, marar TLS, RabbitConnectionFactoryBean na Spring na iya ba da masana'antar socket mai sane da SOCKS ga abokin ciniki na RabbitMQ Java.

Idan Commons Net ya riga ya wanzu, saita factory bean ɗin da ke akwai kafin farawa:

var socksProxy = new java.net.Proxy(
    java.net.Proxy.Type.SOCKS,
    new java.net.InetSocketAddress("proxy.example", 1080));
rabbitFactoryBean.setSocketFactory(
    new org.apache.commons.net.DefaultSocketFactory(socksProxy));

rabbitFactoryBean ita ce RabbitConnectionFactoryBean ta aikace-aikacen. Ka riƙe mai masaukin broker, tashar AMQP, asusu da tsarin kula da haɗin Spring. Broker ɗin ya kasance makoma; SocketFactory na ƙirƙirar sockets ɗin da suke isa gare shi ta SOCKS. Don gwaji marar mahimmanci a kan broker na jama'a inda aka ba da izinin masu shiga tsakani na jama'a, jerin wakilan SOCKS yana ba da 'yan takara; daidaita da sigar SOCKS da runtime ke tallafawa sannan tabbatar da shiga ainihin mai masaukin broker da tasharsa.

Masana'antar Commons Net na ƙirƙirar java.net.Socket marar haɗi ta amfani da Proxy da aka bayar. Sannan lambar haɗin mai toshewa ta RabbitMQ ta haɗa wannan socket ta hanyar haɗin da ta saba. Fitar da HTTP_PROXY kawai ba ya samar da wannan masana'antar socket ta AMQP.

RabbitMQ ya rubuta cewa ƙugiya ta SocketFactory ta shafi I/O mai toshewa. Abokin ciniki da aka saita don NIO ko wata hanyar jigila yana buƙatar ƙugiyar da wannan jigilar ke tallafawa. Don AMQPS, ka riƙe masana'antar socket ta TLS da ta dace da tabbatar da makoma; maye gurbinta da masana'antar sauƙi da ke sama ba cikakken tsarin TLS ba ne.