Beka ingxoxo ye-SOCKS yeNetty ngaphambi kwe-application protocol yakho

Hlela isiphathi se-SOCKS proxy seNetty ngaphambi kwethrafikhi ye-application futhi ugcine indawo engakaxazululwanga lapho i-DNS ohlangothini lwe-proxy ihlosiwe.

Nge-bootstrap/pipeline yeNetty ekhona lapho iseva ye-SOCKS kufanele ixazulule indawo:

bootstrap.resolver(NoopAddressResolverGroup.INSTANCE);

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

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

Iphelo le-proxy iyipothi yasendaweni engu-1080; ilitshe lokuxhumana elingakaxazululwanga yi-example.com:443. Ungasebenzisi ikheli le-proxy kuzo zombili izindima futhi ungaxazululi igama ngaphambi kokuba isiphathi silithole. Ezinhlosweni zomphakathi emzileni we-proxy womphakathi ovunyelwe, uhlu lwe-SOCKS5 proxy luhlinzeka ngabangeneleli bephelo le-proxy lesiphathi.

Beka i-Socks5ProxyHandler ngaphambi kweziphathi ezishintshanisa ithrafikhi yendawo. Linda i-future yoxhumano lwe-proxy, hhayi nje isiteshi esifika kumlaleli. Indlela noma indawo enqatshiwe ingeyalesi sigaba sokusetha.

Ku-HTTPS, ungqimba lwe-TLS olulandelayo lusebenzisa igama lomsingathi wendawo, ukuqinisekisa nokuthembela okudingekayo—hhayi ubunikazi bephelo le-SOCKS. Ngemva kwalokho kuphela kuqala ukushintshana kwe-HTTP/application.

Le ngxenye ayinikezi ama-event loop, izinhlobo zamastheshi, iziphathi ze-TLS/HTTP noma ukuphathwa kwamaphutha okuvamile. Khetha i-SOCKS constructor ehambisana nezidingo zokuqinisekisa; isiphathi se-HTTP Basic kwenye iphrothokholi.

Sebenzisa i-resolver ye-no-op kuphela lapho lesi siphathi sangaphansi siphethe ukuxazululwa kwegama lomsingathi. Ezinye izixhumanisi zingase zidinge ukusesha kwasendaweni. Gcina ihlukanisile imiphumela ye-resolver, i-future ye-proxy, i-TLS kanye nomphumela we-application lapho uhlola ukwehluleka.

Izihloko ezihlobene