setRequestInterception disables caching. I need it not to do that.

[jribbens]

The documentation says that page.setRequestInterception disables "page caching", without explaining what "page caching" is or why it is being disabled. Firstly, it looks like it actually means it disables all caching. Secondly, I need it not to do that. Why does it happen? There is no obvious connection between the two things. If I were to do:

  await page.setRequestInterception(true)
  page.on('request', request => request.continue())
  await page._client.send('Network.setCacheDisabled', { cacheDisabled: false })

would anything bad happen, and if so, what?

[whalderman]

On why that happens: #2905 (comment)
Also see #6996

[jribbens]

I think they're saying that the only problem is that if caching is not disabled, then requests served from the cache will not be intercepted? If so then it would be very much worth saying so in the documentation - I think for my application that wouldn't be a problem at all (if I didn't want to block or alter the request the first time it was issued, I'm unlikely to want to do so on subsequent occasions).

[Androbin]

#7060 was just merged, it solves the issue that originally led to the decision to disable the cache

[jribbens]

#7060 was just merged, it solves the issue that originally led to the decision to disable the cache

Excellent, hopefully there will now be a patch to allow request interception with cache enabled :-)

[Androbin]

@jribbens See #6996, and #7217

[stale]

We're marking this issue as unconfirmed because it has not had recent activity and we weren't able to confirm it yet. It will be closed if no further activity occurs within the next 30 days.

[jribbens]

This issue was fixed in Puppeteer version 9.