To check whether Puppeteer request interception is enabled for a page, track the value your code passes to page.setRequestInterception(). The current documented Page API shows this setter but no page-level getter. By contrast, request-level methods such as request.isInterceptResolutionHandled() tell you whether one particular request has been resolved—not whether interception is enabled for the page.
Track the page setting in your own code
Keep the state in a shared wrapper around page.setRequestInterception(). Update the flag only after the awaited setter succeeds; if the call fails, the local value then continues to reflect the last successful change.
As an Amazon Associate I earn from qualifying purchases.
let requestInterceptionEnabled = false;
async function setRequestInterception(page, enabled) {
await page.setRequestInterception(enabled);
requestInterceptionEnabled = enabled;
}
function isRequestInterceptionEnabled() {
return requestInterceptionEnabled;
}Use the wrapper wherever your application changes interception. If multiple components can call the Puppeteer setter directly, their changes can bypass the flag and make it inaccurate. Put the page and its interception bookkeeping under one shared owner.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →This flag records the state your application knows about; it is not a Puppeteer-provided getter. The current Page API documents setRequestInterception(), but the current Page reference does not document a page-level state getter. The docs surfaced for Puppeteer 25.12.0; check the reference matching your installed version when upgrading.
#1 Best Overall
Do not confuse page configuration with request resolution
Puppeteer exposes methods for checking the resolution state of an individual HTTPRequest. These answer a different question from whether interception is enabled on the page.
| Question | What to check | Scope |
|---|---|---|
| Is interception enabled for this page? | Your application-side flag around page.setRequestInterception() |
Page configuration |
| Has this request already been resolved? | request.isInterceptResolutionHandled() or request.interceptResolutionState() |
One request |
See Puppeteer’s request interception guide for the request-level methods and their behavior.
Rank #2
Resolve intercepted requests promptly
Once interception is enabled, each request stalls unless it is continued, answered, aborted, or completed from the browser cache, as the Puppeteer API reference explains. Register a handler that resolves requests before navigation or other page activity that can issue them. The documented resolution methods are request.continue(), request.respond(), and request.abort(); the HTTPRequest API says they require interception to be enabled and can throw immediately if it is not.
When handlers perform asynchronous work, another handler may resolve the request while the first is waiting. Check whether resolution has already been handled both before starting and after the await:
page.on('request', async request => {
if (request.isInterceptResolutionHandled()) return;
await doAsyncChecks(request);
// Another handler may have resolved it during the await.
if (request.isInterceptResolutionHandled()) return;
await request.continue();
});Without the second check, a competing handler can cause a duplicate resolution attempt and an “Request is already handled!” error. For more complex handler coordination, consult the guide’s documented resolution-state behavior rather than treating a request-level check as the page’s global setting.
Account for authentication enabling interception
page.authenticate() enables request interception behind the scenes to implement HTTP authentication, and Puppeteer notes this may affect performance. If you maintain application-side state, account for authentication setup in the same bookkeeping or make its effect explicit in your page owner. The API documentation does not establish that disabling interception is automatically safe while authentication is configured, so do not assume that behavior without checking the implementation for your Puppeteer version. See the authentication API reference.
Troubleshooting
- Your flag says disabled, but interception appears active: Find calls to
page.authenticate()and any direct calls topage.setRequestInterception()that bypass the wrapper; include them in the shared state ownership. - A request hangs after enabling interception: Ensure a request handler is installed before navigation and that every path resolves the request by continuing, responding, or aborting it.
- You see “Request is already handled!”: Multiple handlers may be resolving the same request. Check
isInterceptResolutionHandled()before and after asynchronous work. continue(),respond(), orabort()throws: Confirm interception is enabled for the page and that another handler has not already resolved the request.
Or skip the browser setup
If your goal is to capture a website image or PDF rather than manage Puppeteer directly, ScreenshotNeo provides a one-call screenshot API. Cookie banners, popups, and chat widgets are removed before the shot; bot checks, blank pages, and failed loads are never billed. Its MCP server lets AI agents take screenshots, and 1,000 screenshots a month are free with no card; paid plans start at $5 for 3,000.
Recommended Free Tools
Example cURL request (see the ScreenshotNeo API documentation):
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpLearn about ScreenshotNeo, or sign up for 1,000 free screenshots a month with no card.
Quick Recap
Best Value
- Used Book in Good Condition
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
