Bug 1123920 - requestStart timestamp is before connectEnd when using persistent connections r=mcmanus

This commit is contained in:
Valentin Gosu 2015-02-25 20:23:35 +02:00
parent bd5a20075a
commit 3de704d5e7
2 changed files with 6 additions and 18 deletions

View File

@ -511,7 +511,12 @@ nsHttpTransaction::OnTransportStatus(nsITransport* transport,
LOG(("nsHttpTransaction::OnSocketStatus [this=%p status=%x progress=%lld]\n",
this, status, progress));
if (TimingEnabled()) {
// If the timing is enabled, and we are not using a persistent connection
// then the requestStart timestamp will be null, so we mark the timestamps
// for domainLookupStart/End and connectStart/End
// If we are using a persistent connection they will remain null,
// and the correct value will be returned in nsPerformance.
if (TimingEnabled() && GetRequestStart().IsNull()) {
if (status == NS_NET_STATUS_RESOLVING_HOST) {
SetDomainLookupStart(TimeStamp::Now());
} else if (status == NS_NET_STATUS_RESOLVED_HOST) {

View File

@ -1,17 +0,0 @@
[test_resource_timing.html]
type: testharness
[PerformanceEntry has correct name, initiatorType, startTime, and duration (link)]
disabled: https://bugzilla.mozilla.org/show_bug.cgi?id=1079837
[PerformanceEntry has correct order of timing attributes (iframe)]
disabled: https://bugzilla.mozilla.org/show_bug.cgi?id=1079837
[PerformanceEntry has correct order of timing attributes (link)]
disabled: https://bugzilla.mozilla.org/show_bug.cgi?id=1079837
[PerformanceEntry has correct order of timing attributes (script)]
disabled: https://bugzilla.mozilla.org/show_bug.cgi?id=1079837
[PerformanceEntry has correct order of timing attributes (xmlhttprequest)]
disabled: https://bugzilla.mozilla.org/show_bug.cgi?id=1079837