Network monitor & HTTP
Two complementary network features sit on the CDP Network domain:
- Network monitor —
tab.monitor()(featuremonitor) is a long-livedStream<NetworkEvent>of completed HTTP exchanges, WebSocket frames, and EventSource messages. Passive: it observes, never modifies. - Browser-context HTTP —
tab.request()(always available) makes an HTTP request from the browser context, inheriting the page's cookies and CORS, with an opt-in privileged bypass.
For one-shot "await the next response and assert on it" use the
expect surface instead; for modifying or blocking
requests use Interception (the active Fetch
domain). The monitor is the persistent, read-only generalization of
expect_response.