New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
a bit confused with the "Redirect" timing in Time Navigation #132
Comments
You're correct, in the case of same-site redirections, the "cost" of the initial DNS and TCP will likely be as part of the first request, whose timestamps get reduced into just the the duration of Since the DNS and TCP are likely re-used for those same-site redirections, the "final" request (that's reported in the other NavigationTiming timestamps) will likely have its DNS and TCP durations be 0-ish (e.g. |
Thanks ! |
In practice, this is what we see in RUM data. Feel free to share any examples if you see differently! |
I believe we've addressed this question, but please leave a comment if there's anything else! |
In the time navigation timeline, redirect occurs before any request on the network (DNS, TCP/TLS establishment,...).
But if I surf a site and receive a status code 3xx to redirect my request, it means that I've established a TCP connection to this server.
So what does the redirect part of the time navigation take into account ?
The text was updated successfully, but these errors were encountered: