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
I have a HAR file produced with Chrome. As the title says, it looks like one transaction is shown incorrectly. All the numbers are correct, but the bar placement/sizing is incorrect (relative to the bars for other transactions on the page). The other transactions on the page all finish within about 1.5 seconds (onLoad is ~750ms). The transaction that appears to be incorrect starts 12 seconds after the page start and lasts ~200ms. But on the chart, it is shown starting at page-start and the bar for the transaction spans the entire chart. The transaction duration is ~1/4 of the transaction above it, but is shown as a bar twice as long. The transaction is a post that leads to the next page. Is this a know problem in this situation? Or am I not reading the chart correctly?
Hi, I think this is deliberate. I think that if there is a long enough time gap between requests then HAR Viewer will draw a slightly thicker line between requests and draw the new request at the left-hand margin (see the arrows below, pointing to the thicker line and the new request at the left-hand margin).
This behaviour is to avoid the timeline getting 'too wide', or the request bars getting 'too small' relative to the total elapsed time.
I'll need to double-check the code, but I think that's what's happening.
UPDATE - I think HAR Viewer calls these breaks in the request list 'phases' - see
There is a cookie value called phaseInterval that can be set to a value in milliseconds. This defaults to 4000ms. So if two requests are separated by 4 seconds, by default they will be broken into two separate 'phases'. You should be able to manually set this cookie and see the effects.
So because your post.php request starts at 2018-08-09T14:06:36.487Z and the favicon.ico request started maybe a couple of seconds after page start (at 2018-08-09T14:06:24.487Z), this is >= 4 seconds, and so will trigger a new phase.
UPDATE 2 - The splitting of requests into phases will only happen to requests that are started after the onLoad time.
I have a HAR file produced with Chrome. As the title says, it looks like one transaction is shown incorrectly. All the numbers are correct, but the bar placement/sizing is incorrect (relative to the bars for other transactions on the page). The other transactions on the page all finish within about 1.5 seconds (onLoad is ~750ms). The transaction that appears to be incorrect starts 12 seconds after the page start and lasts ~200ms. But on the chart, it is shown starting at page-start and the bar for the transaction spans the entire chart. The transaction duration is ~1/4 of the transaction above it, but is shown as a bar twice as long. The transaction is a post that leads to the next page. Is this a know problem in this situation? Or am I not reading the chart correctly?
This is the page section of the HAR:
And this is the entry:
The text was updated successfully, but these errors were encountered: