Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Network.requestIntercepted does not intercept requests when chrome is started with a new user-data-dir for the first time
See original GitHub issueWhen attempting to run the code from Intercept-and-block-requests-by-URL the first time chrome is started with a new user-data-dir Network.requestIntercepted doesn’t intercept requests. If Chrome is stopped and started again with the same user-data-dir it works as expected. This only happens when not using the --headless flag. When used in conjunction with chrome-launcher it seems as though the code doesn’t work as chrome-launcher creates a new user-data-dir every time. Here is a repo demonstrating this behavior: https://github.com/JarrodCTaylor/cri-request-interception
| Component | Version |
|---|---|
| Operating system | macOS Sierra 10.12.6 |
| Node.js | 8.2.1 |
| Chrome/Chromium/… | 61.0.3163.79 |
| chrome-remote-interface | 0.24.5 |
Is Chrome running in a container? NO
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Related Google Group post: https://groups.google.com/forum/#!topic/chrome-debugging-protocol/YC6LbG8lls0
crbug link: https://bugs.chromium.org/p/chromium/issues/detail?id=764505