[Feature Request] [Pull Request?] Declare Request._requestId or Request._interceptionId in the API

When you intercept or inspect a request via the DevTools protocol, you use a special InterceptionId or RequestId. Can you expose these properties via the Request object? I can already see that they are kept tracked of in the _interceptionId and _requestId fields, respectively, but they are undocumented and meant to be private.

Since this is a standard feature of the DevTools protocol, it seems to make sense to expose them. If it’s okay by you, I will submit a pull request that does this myself.

Use cases:

1. Allows using puppeteer and a lower-level DevTools client together for things puppeteer does not support.
2. The properties are useful in and of themselves. For example, from my research, _interceptionId can be used to keep track of a series of redirects.

[GregRos]

@aslushnikov That’s great! I’m looking forward to contributing something myself.

[aslushnikov]

@GregRos thank you for taking time and explaining me your usecase.

If your API can work even on the Request object passed in the handler, and the parent requests always maintain reference identity with the objects that were sent to the handler last time, that’s great!

@GregRos this would be the case. Closing this in favor of #1816.