NavigationTiming redirectStart and redirectEnd properties not populated

RESOLVED INVALID

Status

()

Core
Document Navigation
RESOLVED INVALID
4 years ago
4 years ago

People

(Reporter: matthew.d.freake, Unassigned)

Tracking

25 Branch
x86_64
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

4 years ago
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.0) Gecko/20130724 Firefox/25.0 (Nightly/Aurora)
Build ID: 20130724222711

Steps to reproduce:

Using Nightly 25.0.a1 I go to http://webtimingdemo.appspot.com/ and tick HTTP redirect. I then click 'Try It'


Actual results:

The NavigationTiming object displayed is:

All properties

type: Navigate
redirectCount: 0
navigationStart: 1374751139935 0ms
unloadEventStart: 1374751140464 529ms
unloadEventEnd: 1374751140465 530ms
redirectStart: 0 n/a
redirectEnd: 0 n/a
fetchStart: 1374751140311 376ms
domainLookupStart: 1374751140311 376ms
domainLookupEnd: 1374751140311 376ms
connectStart: 1374751140311 376ms
connectEnd: 1374751140311 376ms
requestStart: 1374751140316 381ms
responseStart: 1374751140464 529ms
responseEnd: 1374751140464 529ms
domLoading: 1374751140464 529ms
domInteractive: 1374751140575 640ms
domContentLoadedEventStart: 1374751140613 678ms
domContentLoadedEventEnd: 1374751140616 681ms
domComplete: 1374751140616 681ms
loadEventStart: 1374751140616 681ms
loadEventEnd: 1374751140717 782ms
legacyNavigationStart: 1374751140472 537ms


Expected results:

I would expect 
redirectStart: 0 n/a
redirectEnd: 0 n/a
to have actual values.

I get the same result on a locally developed site which submits a POST and gets a 302 back redirecting Firefox to another page.

This expectation is based on the NavigationTiming document on the W3c site (http://www.w3.org/TR/navigation-timing/) , which says

"If there are HTTP redirects or equivalent when navigating and if all the redirects or equivalent are from the same origin, this attribute must return the starting time of the fetch that initiates the redirect. Otherwise, this attribute must return zero."

Updated

4 years ago
Component: Untriaged → Document Navigation
Product: Firefox → Core
Matthew, the spec says:

  and if all the redirects or equivalent are from the same origin

In this case, the redirect is crossing origins: the pre-redirect URI is at http://stevesouders.com while the post-redirect URI is at http://webtimingdemo.appspot.com

Marking invalid, but if you have a testcase which has this behavior for same-origin redirects please do reopen.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.