search

w3c / server-timing

Server Timing
http://w3c.github.io/server-timing/
Other
75 stars 20 forks source link

readdress TAO #35

Closed cvazac closed 7 years ago

cvazac commented 7 years ago

(see: https://w3c.github.io/server-timing/#cross-origin-resources)

For non same-origin resources, we zero-out the duration and description fields. I don't think that's enough. duration and description are both optional - the mere presence of a server-timing metric with a particular name (eg. Server-Timing: cache-hit) is enough to communicate boolean information. I propose that we completely ignore all server timing headers for resources that do not pass the "timing allow check" algorithm.

cc @igrigorik @yoavweiss

yoavweiss commented 7 years ago

Makes sense to me to drop entries to the floor if "timing allow check" doesn't pass

igrigorik commented 7 years ago

Yep, that makes sense. 👍

igrigorik commented 7 years ago

Resolved via #36.