Hortaal wada-hadalka SOCKS ee Netty ka hor borotokoolka codsigaaga

Amar handler-ka proxy-ga SOCKS ee Netty ka hor taraafikga codsiga oo ilaali goob aan la xallin marka DNS dhinaca proxy-ga loo qasdo.

Bootstrap/pipeline Netty oo jira halkaas oo server-ka SOCKS ay tahay inuu xalliyo goobta:

bootstrap.resolver(NoopAddressResolverGroup.INSTANCE);

pipeline.addFirst(
    new Socks5ProxyHandler(new InetSocketAddress("127.0.0.1", 1080))
);

bootstrap.connect(
    InetSocketAddress.createUnresolved("example.com", 443)
);

Dhammaadka proxy-ga waa port maxalli 1080; bartilmaameedka xiriirka aan la xallin waa example.com:443. Ha isticmaalin cinwaanka proxy-ga labada door mana xallin magaca ka hor inta uusan handler-ku helin. Bartilmaameedyada dadweynaha ee wadada proxy-ga dadweynaha ee la ogolaaday, liiska proxy-ga SOCKS5 wuxuu bixiyaa musharixiin dhammaadka proxy-ga handler-ka.

Dhig Socks5ProxyHandler ka hor handler-yada isweydaarsada taraafikga goobta. Sug future-ka xiriirka proxy-ga, ma aha oo kaliya kanaal gaaraya dhegeystaha. Hab ama goob la diiday waxay ka tirsan tahay marxaladdan dejinta.

HTTPS, lakabka TLS ee xiga wuxuu isticmaalaa magaca martigeliyaha goobta, xaqiijinta iyo kalsoonida loo baahan yahay—ma aha aqoonsiga dhammaadka SOCKS. Markaas ka dib ayaa isweydaarsiga HTTP/codsiga bilaabmaa.

Qaybtan ma bixiso wareegyo dhacdooyin, noocyada kanaalka, handler-yada TLS/HTTP ama maaraynta khaladaadka caadiga ah. Dooro constructor-ka SOCKS ee waafaqsan baahida xaqiijinta; handler-ka HTTP Basic waa borotokool kale.

Isticmaal resolver-ka no-op kaliya halkaas oo handler-kan hoose uu leeyahay xallinta magaca martigeliyaha. Xiriirada kale waxay u baahan karaan raadin maxalli ah. Kala sooc wax-soo-saarka resolver-ka, future-ka proxy-ga, TLS iyo natiijada codsiga marka aad baarayso cilad.

Maqaallo la xiriira