Unable to page.setRequestInterception(true) if connecting to chrome

For the browser instance puppeteer.launch it can do somethings like

await page.setRequestInterception(true);
page.on('request', request => {
    if (request.resourceType() === 'image') {
        request.abort();
    }
    else {
        request.continue();
    }
});

But it can not setRequestInterception(true) for a chrome instance ( I do puppeteer connect with chromelaucher or create a chrome with remote debug port manually)

[jazoom]

So why exactly was this closed? The issue remains.

[jazoom]

  let browser;
  try {
    browser = await puppeteer.launch({
      headless: false,
      executablePath: 'chrome.exe',
      args: [`--proxy-server=${options.proxy.ip}:${options.proxy.port}`]
    });

    const page = await browser.newPage();
    await page.setViewport({ width: 800, height: 600 });

    await page.setRequestInterception(true);
    page.on('request', interceptedRequest => {
      console.log('YOU WILL NEVER SEE THIS LOGGED');
      if (['image', 'media', 'font', 'stylesheet'].includes(interceptedRequest.resourceType())) {
        return interceptedRequest.abort();
      }
      interceptedRequest.continue();
    });

    const response = await page.goto(options.url);

    const source = await response.text();

    const content = await page.content();

  } catch (error) {
  }

  browser && await browser.close();

@aslushnikov Since you’re already interpreting that code, can you see why response would be null? I got it from your comment here (https://github.com/GoogleChrome/puppeteer/issues/749#issuecomment-328600349). Unfortunately, response is always null so trying to get text() from it causes a TypeError.

Edit: I think response being null is related to the interception failure. The following is never logged:

    page.on('response', resp => {
      console.log('GOT A RESPONSE, YO');
    });