[Webkit-unassigned] [Bug 103867] [Resource Timing] Record redirectStart & redirectEnd time and expose in resource timing entries
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Thu Jan 17 11:44:07 PST 2013
https://bugs.webkit.org/show_bug.cgi?id=103867
--- Comment #13 from James Simonsen <simonjam at chromium.org> 2013-01-17 11:45:54 PST ---
(In reply to comment #12)
> in section4.3, startTime should be initiationTime(redirectStart) when if all the redirects or equivalent are from the same origin as the current document or the Timing-Allow-Origin HTTP response header rules are met.
> now, as my understand, my case2 in comment #10 should be:
> case 2: although Ri and Doc D are not the same origin, response of Ri allow-timing by Doc D's origin.
> then startTime should be initiationTime(first) or final resource fetch time(last), then why we reset the initiationTime? startTime in processing model never changed after 3.2.
>
> what is more puzzled me is in processing model 3.19a, redirectStart is reset according to "current resource and the resource that is redirected to"
I believe the processing model is correct. We should probably bring this up on the public-webperf mailing list though.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list