Sanya tattaunawar SOCKS ta Netty kafin ka'idar aikace-aikacenka

Don bootstrap/pipeline na Netty da ke akwai inda ya kamata uwar garken SOCKS ya warware makoma:

bootstrap.resolver(NoopAddressResolverGroup.INSTANCE);

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

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

Ƙarshen wakili shine tashar gida 1080; makasudin haɗin da ba a warware ba shine example.com:443. Kada ka yi amfani da adireshin wakili don ayyukan biyu kuma kada ka warware sunan kafin mai sarrafawa ya karɓe shi. Don makasudi na jama'a a kan hanyar wakilin jama'a da aka yarda, jerin wakilan SOCKS5 yana ba da 'yan takara don ƙarshen wakilin mai sarrafawa.

Sanya Socks5ProxyHandler kafin masu sarrafawa da ke musayar zirga-zirgar makoma. Jira future ɗin haɗin wakilin, ba kawai tashar da ta isa mai sauraro ba. Ƙin hanyar ko makoma na wannan matakin saitin ne.

Don HTTPS, Layer na TLS na gaba yana amfani da sunan mai masaukin makoma, tabbacin da ake buƙata da amincewa—ba asalin ƙarshen SOCKS ba. Sannan ne kawai musayar HTTP/aikace-aikace ke farawa.

Yankin bai bayar da madaukai na abubuwan da suka faru, nau'ikan tashoshi, masu sarrafa TLS/HTTP ko magance kuskure na yau da kullum ba. Zaɓi constructor na SOCKS da ya dace da bukatun tabbatarwa; mai sarrafa HTTP Basic wata ka'ida ce.

Yi amfani da no-op resolver kawai inda wannan mai sarrafawa na ƙasa ke da warware sunan mai masauki. Wasu haɗin kai na iya buƙatar bincike na gida. Raba fitowar resolver, future ɗin wakili, TLS da sakamakon aikace-aikace daban yayin bincikar gazawa.