Tabbatar da wakili a Chrome CDP: kula da dukan hanyoyin abin da ya faru na Fetch

Kunna buƙatun tabbatarwa kafin kewayawa, ci gaba da buƙatun da aka dakatar na yau da kullum, kuma amsa kalubalen Proxy da aka nufa kawai da manufar ƙoƙari mai iyaka.

A cikin zaman CDP da ya dace, yi rijistar masu sarrafawa kafin kewayawa, sannan ka kira Fetch.enable da waɗannan sigogi:

{"handleAuthRequests": true}
Abin da ya faruHanyar amsa da ake bukata
Fetch.requestPausedcontinueRequest tare da wannan requestId lokacin da aikin yau da kullum ya kamata ya ci gaba
Fetch.authRequiredDuba authChallenge, sannan yi amfani da continueWithAuth tare da requestId na abin da ya faru na tabbatarwa

Ga mai shiga tsakani da aka gane, sigogin tabbatarwa su ne:

{
  "requestId": "REQUEST_ID_FROM_AUTH_EVENT",
  "authChallengeResponse": {
    "response": "ProvideCredentials",
    "username": "PROXY_USERNAME",
    "password": "PROXY_PASSWORD"
  }
}

Tabbatar authChallenge.source shine Proxy kuma asalinsa shine mai kalubalanci da aka nufa kafin loda asusun daga tushen shaidar. Kalubalen Server yana bin wata manufar tabbatarwa.

Bibiyi ƙoƙarin da aka yarda da shi ga kowace buƙata da aka kama; kalubalen da aka ƙi akai-akai ya kamata ya karɓi CancelAuth, ba wani sallama marar ƙarewa ba. Share bin diddigin a lokacin kammalawa ko rufe zaman.

Idan shafin ya tsaya, duba kuma abubuwan da suka faru na requestPaused da ba a warware ba. Sarrafa tabbatarwa baya ci gaba da su kai tsaye, kuma babu ɗayan hanyoyin abubuwan da ya faru da ke zaɓar hanyar wakili ta burauza.

Labarai masu alaƙa