Change Details

Currently the server-timing header only expose the cache status (hit, miss, pass, etc.). In order to restore the ability to collect per-host data in the navtiming daemon, we need a way for the client code to know which DC/host served the request to them. This can be achieved by extending the contents of the server-timing header to also include the name of the cache host that served the request.

Currently the server-timing header only expose the cache status (hit, miss, pass, etc.). In order to restore the ability to collect per-host data in the navtiming daemon, we need a way for the client code to know which DC/host served the request to them. This can be achieved by extending the contents of the server-timing header to also include the name of the cache host that served the request. For example, instead of this: ``` server-timing: cache;desc="pass" ``` We could serve this: ``` server-timing: cache;desc="pass", host;desc="cp3056" ```

Currently the server-timing header only expose the cache status (hit, miss, pass, etc.). In order to restore the ability to collect per-host data in the navtiming daemon, we need a way for the client code to know which DC/host served the request to them. This can be achieved by extending the contents of the server-timing header to also include the name of the cache host that served the request. For example, instead of this: ``` server-timing: cache;desc="pass" ``` We could serve this: ``` server-timing: cache;desc="pass", host;desc="cp3056" ```