SOCKS proxies a cikin .NET HttpClient: hanyoyin URI da ake tallafawa
Yi amfani da rubutattun hanyoyin URI na SOCKS proxy na mai sarrafa .NET HTTP da ya dace maimakon ɗauka cewa tsofaffin hanyoyin wasu na uku har yanzu suna da bukata.
Tsofaffin amsoshi suna ba da shawarar ƙarin mai sarrafa SOCKS saboda suna yin nuni ga tsohuwar tarin hanyar sadarwa ta .NET. Sabon tarin .NET HTTP da ake tallafawa zai iya amfani da rubutattun hanyoyin URI na SOCKS proxy.
var handler = new HttpClientHandler
{
Proxy = new WebProxy("socks5://203.0.113.10:1080"),
UseProxy = true
};
using var client = new HttpClient(handler);Ƙarshen wurin misali ne kawai. Jerin SOCKS5 proxy yana ba da ƴan takara na jama'a don wannan URI na socks5 WebProxy; yi amfani da sigar da ainihin mai sarrafawa ke tallafawa. Duba tsarin manufa, lokacin aiki, dandamali da ainihin mai sarrafawa da aikace-aikacen ke amfani da su kafin ka yi amfani da wannan misalin akan tsohon tsarin .NET Framework.
Rubutun Microsoft na yanzu game da proxy ya lissafa socks4, socks4a da socks5. Waɗannan sunaye suna bayyana halin yarjejeniya. Lambar tashar jiragen ruwa kaɗai ba ta zaɓi sigar SOCKS ba, kuma rubutun socks5h na curl ba wata ƙa'idar URI ce ta duniya da kowane abokin ciniki ke karɓa ba.
Don sabis ɗin SOCKS5 mai tabbatarwa, saita bayanan shiga bisa ga hanyar da mai sarrafawa ke tallafawa. SOCKS4 da SOCKS4a ba sa ba da irin wannan hanyar tabbatar da kalmar sirri.
URL ɗin manufa ya kasance ba ya canzawa. Buƙatar HTTPS har yanzu tana kafa da tabbatar da TLS na manufa ta hanyar proxy; ƙara SOCKS ba dalili ba ne na kashe wannan tabbaci.