Network.responseReceivedExtraInfo may be fired before or after responseReceived.

[ifduyue]

From https://chromedevtools.github.io/devtools-protocol/tot/Network/#event-responseReceivedExtraInfo

responseReceivedExtraInfo may be fired before or after responseReceived.

And reading code at

chrome-har/index.js

Lines 317 to 362 in 7a821bb

	case 'Network.responseReceivedExtraInfo':
	{
	if (pages.length < 1) {
	//we haven't loaded any pages yet.
	continue;
	}
	if (ignoredRequests.has(params.requestId)) {
	continue;
	}
	let entry = entries.find(
	entry => entry._requestId === params.requestId
	);
	if (!entry) {
	entry = entriesWithoutPage.find(
	entry => entry._requestId === params.requestId
	);
	}
	if (!entry) {
	debug(
	`Received response extra info for requestId ${
	params.requestId
	} with no matching request.`
	);
	continue;
	}
	if (!entry.response) {
	// Extra info received before response
	entry.extraResponseInfo = {
	headers: parseHeaders(params.headers),
	blockedCookies: params.blockedCookies
	};
	continue;
	}
	if (params.headers) {
	entry.response.headers = entry.response.headers.concat(
	parseHeaders(params.headers)
	);
	}
	}
	break;

Only responseReceivedExtraInfo fired after responseReceived was handled.

[ifduyue]

             if (params.headers) { 
               entry.response.headers = entry.response.headers.concat( 
                 parseHeaders(params.headers) 
               ); 
             } 

Also responseReceivedExtraInfo.headers and responseReceived.headers are almost identical, so here concat is a bug too?

[soulgalore]

Hi @ifduyue ok cool. Do you have time to make PR to fix it or do you have an example trace where it's out of order, then we can setup a test case for it so we know it's fixed?

[ifduyue]

Hi @soulgalore, OK, I'll try