Izimpendulo zakudala ziphakamisa umphathi we-SOCKS owengeziwe ngoba ziqondise ku-.NET network stack endala. I-.NET HTTP stack yesimanje esekelwayo ingasebenzisa izinhlelo ze-URI ze-SOCKS proxy ezibhalwe phansi.

var handler = new HttpClientHandler
{
    Proxy = new WebProxy("socks5://203.0.113.10:1080"),
    UseProxy = true
};
using var client = new HttpClient(handler);

Iphuzu lokugcina liyisibonelo kuphela. Uhlu lwama-proxy e-SOCKS5 luhlinzeka ngabantu abavela emphakathini kulobu URI se-socks5 se-WebProxy; sebenzisa inguqulo esekelwa umphathi wangempela. Hlola uhlaka oluqondiwe, isikhathi sokusebenza, inkundla kanye nomphathi wangempela osetshenziswa uhlelo ngaphambi kokusebenzisa lesi sibonelo kunqubo endala ye-.NET Framework.

Imibhalo yamanje ye-proxy ye-Microsoft ibala i-socks4, i-socks4a ne-socks5. Lawo magama achaza ukuziphatha kweprotocol. Inombolo yembobo yodwa ayikhethi inguqulo ye-SOCKS, futhi isipelingi se-socks5h se-curl akulona uhlelo lwe-URI jikelele olwamukelwa yiklayenti ngayinye.

Ngemsebenzi we-SOCKS5 oqinisekisiwe, lungiselela imininingwane yokungena ngokwesixhumi esibonakalayo esekelwa umphathi. I-SOCKS4 ne-SOCKS4a azinikezi indlela efanayo yokuqinisekisa iphasiwedi.

I-URL yendawo ekuyiwa kuyo ihlala ingashintshi. Isicelo se-HTTPS sisamisa futhi siqinisekisa i-TLS yendawo ekuyiwa kuyo ngomzila we-proxy; ukwengeza i-SOCKS akusona isizathu sokucisha lokho kuqinisekisa.

Izihloko ezihlobene