Bugzilla

(In reply to Peter Hedenskog from comment #30)
> Hi Henrik, sorry that it took so long to get back. There's two things I think:

No worries at all. :) Some times it can take longer...

> - Clear browser cache - I remember seeing something about but I haven't implemented that on the Browsertime side.

It's not about clearing the cache but about bypassing the cache. The BiDi command to set the network cache mode is:
https://w3c.github.io/webdriver-bidi/#command-network-setCacheBehavior

> - And one thing that I missed from the beginning, sorry: Getting hold of a response body (as in https://github.com/firefox-devtools/bidi-har-export/issues/22) - For Chrome when we generate a HAR file we use CDP Network.getResponseBody to get hold of the body. The reason why I missed that is that in the old https://github.com/firefox-devtools/har-export-trigger it happened automatically. There's two reasons I know today why it's used: 
> - We use that part in Chrome to know exactly what code was tested in our monitoring. Like for example we monitor and run test against Wikipedia 24/7. We have a regression and by looking at the actual HTML/JavaScript/CSS we could see what changed. It also has helped us to see missmatches in our caching structure (for example one node serving X content but our rests hits another node that serves Y).
> - The extra info is used by tools that analyse which tools has been used to generate the page (e.g wappalyzer)

This is not yet specified and covered by https://github.com/w3c/webdriver-bidi/issues/541. Once it's clear how it works we can reference the appropriate bugs.

(In reply to Peter Hedenskog from comment #30)
> Hi Henrik, sorry that it took so long to get back. There's two things I think:

No worries at all. :) Some times it can take longer...

> - Clear browser cache - I remember seeing something about but I haven't implemented that on the Browsertime side.

It's not about clearing the cache but about bypassing the cache. The BiDi command to set the network cache mode is:
https://w3c.github.io/webdriver-bidi/#command-network-setCacheBehavior

> - And one thing that I missed from the beginning, sorry: Getting hold of a response body (as in https://github.com/firefox-devtools/bidi-har-export/issues/22) - For Chrome when we generate a HAR file we use CDP Network.getResponseBody to get hold of the body. The reason why I missed that is that in the old https://github.com/firefox-devtools/har-export-trigger it happened automatically. There's two reasons I know today why it's used: 
> - We use that part in Chrome to know exactly what code was tested in our monitoring. Like for example we monitor and run test against Wikipedia 24/7. We have a regression and by looking at the actual HTML/JavaScript/CSS we could see what changed. It also has helped us to see missmatches in our caching structure (for example one node serving X content but our rests hits another node that serves Y).
> - The extra info is used by tools that analyse which tools has been used to generate the page (e.g wappalyzer)

This is not yet specified and covered by https://github.com/w3c/webdriver-bidi/issues/747. Once it's clear how it works we can reference the appropriate bugs.