Replies: 1 comment 11 replies
-
I am having the exact same issue as you by the way. Have not found a solution so far. |
Beta Was this translation helpful? Give feedback.
11 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am trying to use the Fetch CDP domain, and have set up a very basic example of adding a handler for cdp.fetch.RequestPaused, and for now I am just responding with a fetch.continue_frequest (https://chromedevtools.github.io/devtools-protocol/tot/Fetch/#method-continueRequest) command whenever the request is paused.
Oddly, the handler is called once for the main page loads html, but the next page resource (in this case a javascript file network request) never reaches this handler, so it stays in a hung state. So the browser tab remains in a spinning stage, and the code flow does not proceed either in python... Screenshot of Network (see the Status for api.js as Pending) and CDP Protocol in Dev Tools.
To diagnose this further, I turned on debug logging to see if the websocket is actually receiving the second "Fetch.requestPaused" message, for the the screenshot above, and turns out it is (see log entries below).. but the second message is somehow never processed by nodriver, and sent to the callback.
Is this working as intended, or what am I doing incorrectly?
Attached full logs for reference.
github_bug_log.txt
Beta Was this translation helpful? Give feedback.
All reactions