Closed mikedijkstra closed 4 years ago
I've come across an issue where headers are missing from requests and responses despite being sent by the browser.
There was an update in Chrome which introduced new protocol events that contain request information from network service. This change introduced Network.requestWillBeSentExtraInfo and Network.responseReceivedExtraInfo events in the devtools log.
Comparing the HAR generated by the Chrome Browser to one from chrome-har you can see the extra information is grouped into the request.
chrome-har
Using the request for a CSS file as an example, you can see in the Devtools logs that there is a Network.requestWillBeSentExtraInfo and a Network.responseReceivedExtraInfo but this extra information is not present in a har generated by chrome-har while it is present in a har generated by the chrome web inspector.
Network.requestWillBeSentExtraInfo
Network.responseReceivedExtraInfo
I'm happy to put together a PR to include this information in chrome-har the same way it's included by the Chrome Browser.
Hi @mikedijkstra aha cool, yes please :)
I've come across an issue where headers are missing from requests and responses despite being sent by the browser.
There was an update in Chrome which introduced new protocol events that contain request information from network service. This change introduced Network.requestWillBeSentExtraInfo and Network.responseReceivedExtraInfo events in the devtools log.
Comparing the HAR generated by the Chrome Browser to one from
chrome-har
you can see the extra information is grouped into the request.Using the request for a CSS file as an example, you can see in the Devtools logs that there is a
Network.requestWillBeSentExtraInfo
and aNetwork.responseReceivedExtraInfo
but this extra information is not present in a har generated by chrome-har while it is present in a har generated by the chrome web inspector.I'm happy to put together a PR to include this information in
chrome-har
the same way it's included by the Chrome Browser.