Ngemva kokuthi isicelo se-WinHTTP sithole i-407, sebenzisa WinHttpQueryAuthSchemes ukuhlola izindlela ezinikeziwe futhi ukhethe eyodwa esekelwa yiklayenti kanye ne-akhawunti. Setha ubufakazi kuleso sicelo:

WinHttpSetCredentials(
    requestHandle,
    WINHTTP_AUTH_TARGET_PROXY,
    selectedScheme,
    proxyUser,
    proxyPassword,
    nullptr);

I-agumenti yokugcina egcinwe kufanele ibe ngu-null. Hlola umphumela we-Boolean futhi uma kwehluleka GetLastError. Impumelelo isho ukuthi i-API yamukele isilungiselelo, hhayi ukuthi i-proxy yamukele ukungena.

Thumela futhi ngokugeleza kokuqinisekisa okulawulwayo futhi uhlole impendulo. Khawulela ukuphinda uzame; umfudlana womzimba wesicelo osusetshenzisiwe kufanele ukwazi ukudlalwa futhi uma umsebenzi uphindwa. I-401 evela endaweni ekuyiwa kuyo isebenzisa WINHTTP_AUTH_TARGET_SERVER, ehlukile kulo mgomo we-proxy.

Lobu bufakazi busebenza esicelweni esisodwa kuphela. I-WinHTTP ayibenzi bube yisitoreji esijwayelekile sobufakazi sezicelo ezizayo. Izixhumanisi eziqinisekisiwe ezisetshenziswa kabusha zingafihla enye inselelo okwesikhashana, ngakho uhlelo lokusebenza kufanele lusabhekana nezinselelo zesikhathi esizayo.

Gcina ukukhethwa kwe-proxy kwehlukile. Intambo yekheli enobufakazi ayithathi indawo yale API ye-handle yesicelo, njengoba nokufinyelela ngempumelelo endaweni yokugcina kungaqedi ukuqinisekisa.

Izihloko ezihlobene