Lolu chungechunge lubonakala lucacile, kodwa ku-.NET 10 luphela ngaphandle kobufakazi beproxy:

proxy.Credentials = new NetworkCredential(proxyUser, proxyPassword);
proxy.UseDefaultCredentials = false;

Ekusebenziseni i-WebProxy ku-.NET 10, ukusetha i-UseDefaultCredentials ku-false kunikeza u-null ku-Credentials. Ukusetha ku-true kukhetha i-CredentialCache.DefaultCredentials. Lezi zakhiwo ezimbili zilawula ukukhetha kwe-akhawunti efanayo.

Nge-akhawunti eqondile yesevisi, nikeza ubufakazi obuhlosiwe ngaphandle kokusetha kabusha ngemuva:

var proxy = new WebProxy("http://proxy.example.net:8080")
{
    Credentials = new NetworkCredential(proxyUser, proxyPassword)
};

Uma ikhodi yokuhlela ekhona kufanele icishe ngokusobala ubufakazi obuzijwayelekile, yenza lokho ngaphambi kokunikeza i-NetworkCredential. I-getter yayo ingaba false kuyilapho ubufakazi obucacile bukhona ngendlela efanele; i-false akusho ukuthi awekho i-akhawunti elungiselelwe.

Namathisela le nto ku-handler eyenza isicelo. Ngokufakazela kwe-Windows okuhlanganisiwe, khetha ngamabomu ubufakazi obuzijwayelekile, usebenzisa ubunikazi obufanele benqubo.

Hlola ukulandelana kwesiqalisi sento nezindlela ezingeziyo mayelana nokunikezwa kwamuva okushintsha i-akhawunti ehlosiwe. Hlanganisa lokhu kuxilonga nokusebenza kwe-WebProxy okusetshenziswayo; impahla enegama elifanayo ku-handler ye-HTTP ingalawula ububanzi bokufakazela obuhlukile.

Izihloko ezihlobene