Closed Bug 1590220 Opened 5 years ago Closed 7 months ago

Implement Network.requestServedFromCache

Categories

(Remote Protocol :: CDP, enhancement, P3)

enhancement

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: impossibus, Unassigned)

References

()

Details

(Whiteboard: [puppeteer-beta2-mvp])

Example:

{"method":"Network.requestServedFromCache","params":{"requestId":"1000019132.777"}}

This is among the events emitted during a gutenberg run: https://wiki.mozilla.org/Remote/PuppeteerCDPUsage#In_Wordpress_gutenberg_test_suite

In Puppeteer:

https://github.com/GoogleChrome/puppeteer/blob/c2651c2b5cc888ebd0ca6be87063d9f98b9eb59c/lib/NetworkManager.js#L241

Whiteboard: [puppeteer-alp
Whiteboard: [puppeteer-alp → [puppeteer-alpha]

In Puppeteer this maps to request._fromMemoryCache, which actually can be retrieved via the property Request.fromCache. Nothing in Gutenberg actually makes use of this property. As such I would suggest that we at least for now do not track this event for the alpha release.

Priority: P2 → P3
Whiteboard: [puppeteer-alpha]

This could probably be implemented by looking at nsIDocShell.loadType.
I’m not sure in which exact order the event is expected.

Whiteboard: [puppeteer-beta2-mvp]
Component: CDP: Network → CDP
Severity: normal → S3
Severity: normal → S3

This was low priority and we are not going to implement this event for CDP.

Status: NEW → RESOLVED
Closed: 7 months ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.