Chrome DevTolls protocol's Fetch.enable does not cause all requests to be intercepted

Asked Nov 23 '20 at 16:09

Active Nov 23 '20 at 16:09

Viewed 1,278 times

I issue a message like this via DevTools Protocol to a running Google Chrome instance:

{
    "id": 0,
    "method": "Fetch.enable",
    "params": {
        "patterns": [{
                "urlPattern": "*.js*",
                "resourceType": "Script",
                "requestStage": "Response"
            }
        ]
    }
}

I was expecting it would cause "Fetch.requestPaused" event for each script file downloaded by a page. It works only for the resources provided in the <head> section of the page, like <script src="..."/>

If the <script src="..."/> is included in any other part of the page (ie. outside of header) it is not being intercepted and no "Fetch.requestPaused" event is issued. Anyone knows how to intercept those reuests (I need to modify the responses before they get to the browser).

asked Nov 23 '20 at 16:09

ed22

1,127
2
14
30

Did you figured this out? – lucaswxp Mar 04 '21 at 14:28
@lucaswxp I used https://github.com/cefsharp/CefSharp which gives much more control and relevant callbacks. – ed22 Mar 04 '21 at 16:52
Did you try other resource types? e.g. `Fetch`, `XHR` or `Document`? – Joren May 03 '21 at 14:50
@Joren, as far as I remember intercepting requests originating from Javascript worked fine. It was a while ago, though. – ed22 May 05 '21 at 08:13

Chrome DevTolls protocol's Fetch.enable does not cause all requests to be intercepted

0 Answers0