We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Server-Timing
In #1895, we added the Server-Timing header to HTTP responses.
https://developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/debugging.html#__server_timing
To namespace metric names we used colons like ssr:route-matching.
ssr:route-matching
It seems like colons (eg. :) are not considered valid characters:
:
https://www.w3.org/TR/server-timing/#the-server-timing-header-field
The result is that tools like Chrome cannot parse our Server-Timing response:
We should consider using a different character for namespacing and verify that it works in Chrome and other Server-Timing parsing tools.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
In #1895, we added the
Server-Timing
header to HTTP responses.https://developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/debugging.html#__server_timing
To namespace metric names we used colons like
ssr:route-matching
.It seems like colons (eg.
:
) are not considered valid characters:https://www.w3.org/TR/server-timing/#the-server-timing-header-field
The result is that tools like Chrome cannot parse our
Server-Timing
response:We should consider using a different character for namespacing and verify that it works in Chrome and other Server-Timing parsing tools.
The text was updated successfully, but these errors were encountered: