You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
one good feature in the future would be to disable getting the content inside of the HAR. Right now it includes everything in the content fields (that's great for debugging) but if it is possible to disable that from a config that would be great (it will make the HAR files so much smaller).
Best
Peter
The text was updated successfully, but these errors were encountered:
Yes, agree. The problem is that chrome.devtools.network.getHAR() method (as designed by chrome does always return the response body. There is no option to exclude it (and e.g. improve performance).
So, this extension can make sure that the response body is not in the result log (if some flag says so) by doing something like:
It would look like as follows from the client perspective:
var options = {
responseBody: false, // Do not include response bodies
};
HAR.triggerExport(options).then(har => {
// length should be smaller if response bodies are not included
var length = JSON.stringify(har.log).length;
var size = getFormattedSize(length);
console.log("HAR log (" + size + ") ", har.log);
});
I don't maybe it doesn't matter if the API always includes? I manually wash it now depending on flags, and I think it's overkill then to include it the trigger?
Hi,
one good feature in the future would be to disable getting the content inside of the HAR. Right now it includes everything in the content fields (that's great for debugging) but if it is possible to disable that from a config that would be great (it will make the HAR files so much smaller).
Best
Peter
The text was updated successfully, but these errors were encountered: