Sababta Java u dooratay SOCKS proxy codsigaaga HTTP

Codsiga Java wuxuu la kulmi karaa dhowr gelin proxy: qaabeynta macmiilka ee cad, dooraha caadiga ah, sifooyinka shabakadda JVM, iyo dejinta nidaamka hawlgalka ee la taageeray. Marka loggu si lama filaan ah u xuso SOCKS, aqoonsado gelinta dooratay.

Koodhka isticmaala dooraha caadiga ah, baadh go'aanka loo qaatay meesha saxda ah:

URI target = URI.create("https://example.com/");
ProxySelector selector = ProxySelector.getDefault();
if (selector != null) {
    System.out.println(selector.select(target));
}

Tani waxay soo sheegtaa musharixiinta dooraha. Ma caddaynayso isku xirnaanta ugu dambeyntii guulaysatay, macmiil leh waddo cad oo u gaar ah wuxuu samayn karaa doorasho kale.

Baadh dejinta shaqeeya

Baadh http.proxyHost, https.proxyHost, socksProxyHost, dekedooyinkooda iyo java.net.useSystemProxies. dukumeentiga JDK ee sifooyinka shabakadda wuxuu sharraxayaa baaxaddooda iyo mudnaantooda. Ogaanshaha proxy-ga nidaamka waxaa la baadhaa bilowga; si ula kac ah u dhig marka JVM la bilaabayo.

Jawaabaha taariikhiga ah waxay sharraxaan isku-darka gaar ah ee wada-hadallada duugga ah ee Windows iyo JDK-yada duugga ah. Warbixinnadaas waxay sharraxi karaan asalka xal, laakiin ma caddaynayaan in runtime-ka hadda uu leeyahay cilad isku mid ah. Diiwaangeli nooca runtime-ka iyo soo-saarka dooraha ka hor intaadan beddelin dejinta nidaamka hawlgalka ee barnaamij kasta.

Haddii barnaamijku u baahan yahay proxy HTTP hal macmiil, qaabeyn proxy oo cad waxay caddayn kartaa shuruuddaas. Haddii uu u baahan yahay marin otomaatig ah oo dhexe, baadh sababta dooruhu u helay ama u soo celiyay gelinta SOCKS ee lama filaanka ah.

Dooraha gaarka ah waa inuu ilaaliyaa ka-gudubka ula kac ah iyo maaraynta guuldarrada. Shaandhaynta musharixiin kasta oo SOCKS ah si aan kala sooc lahayn waxay jebin kartaa isku xirnaan loo malaynayay inay isticmaalaan mid. Hagaaji qaanuunka khaldan ee baaxadda ugu yar ee aad aqoonsan karto.