Note: This is a sanity probe, not a time discipline tool. rtt/2 and browser timers can be noisy, so treat green/red as a hint, not truth, especially on congested factory networks.
Interesting, but why not use the timestamp baked into response headers? There's also domain.tld/cdn-cgi/trace for cloudflare. I don't know how cloudflare will take using that page for this though.
Cross-origin stuff doesn’t always let you get access to those headers and they may not always be there. Some web servers don’t put that there, some do. Some frameworks add them, some don’t.
Note: This is a sanity probe, not a time discipline tool. rtt/2 and browser timers can be noisy, so treat green/red as a hint, not truth, especially on congested factory networks.
Interesting, but why not use the timestamp baked into response headers? There's also domain.tld/cdn-cgi/trace for cloudflare. I don't know how cloudflare will take using that page for this though.
Cross-origin stuff doesn’t always let you get access to those headers and they may not always be there. Some web servers don’t put that there, some do. Some frameworks add them, some don’t.
A simple (and stupid) /time.aspx in VB.NET, because that's what was easily available:
(you need to change "/time" to "/time.aspx" for the original HTML page to work)