Lokacin da WinHTTP ke musanya tsakanin 407 da 401

Buƙatar WinHTTP tana tabbatarwa ga wakili, tana karɓar 401 daga wani shafi, sannan tana samun wata 407 a aika na gaba. Wakili da shafin suna da yanayin tabbatarwa daban, kuma hanyar sake aikawa tana buƙatar riƙe duka biyun.

Misalin tabbatarwa na WinHTTP na asali daga Microsoft yana ajiye tsarin wakilin da aka zaɓa a cikin maɓalli kuma yana sake amfani da asusun wakili kafin kowace WinHttpSendRequest bayan an zaɓi wannan tsari.

1. Aika buƙatar kuma duba amsar.
2. Don 407, tambayi tsare-tsaren da aka bayar kuma ka tuna tsarin wakilin da aka zaɓa.
3. Kafin sake aikawa, ka kira WinHttpSetCredentials don WINHTTP_AUTH_TARGET_PROXY da wannan tsari da asusu.
4. Don 401 daga manufa, sami tsarinta ka saita takardun shaidar uwar garke yayin riƙe yanayin wakilin da aka tuna don aika na gaba.

Misalin ya ambaci musamman sake tabbatarwa bayan ƙalubale daga uwar garke ko turawa a matsayin dalilin sake amfani da takardun shaidar wakili. Sanya kiran a reshen 407 na farko kawai na iya barin wata hanyar sake gwadawa ba tare da shirye-shiryen da ake tsammani ba.

Duba kowace sakamakon API kuma ka iyakance gazawar da ta maimaita. Misalin Microsoft mai taƙaitaccen yana bin diddigin matsayin da ya gabata, yayin da manufar sake gwadawa ta samarwa ya kamata kuma ta gane jerin musanya mai maimaitawa.

Idan mai amfani ya ba da asusun maye gurbin bayan gazawa, sabunta ƙimar da wannan hanyar sake aikawa ke amfani da ita. WinHttpSetCredentials na kowane buƙata ne; ba ajiyar kalmar sirri bace ta dukan tsari da ake maye gurbin abinta don duk buƙatu na gaba.