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
It is currently unspecified as to whether extraneous characters following metric-name should be ignored.
metric-name
We ignore extraneous characters found after a server-timing-param-value, so I'm inclined to do the same for metric-names.
server-timing-param-value
Example:
Server-Timing: metric=;dur=123.4
Note: = is not a legal token character.
=
Options:
parsing should "keep going", yielding: name=metric duration=123.4
parsing should stop, yielding: name=metric duration=0
cc @yoavweiss
The text was updated successfully, but these errors were encountered:
I think it makes sense for us to "keep going", drop parsing when a non-token-char is hit and skip till the next delimiter
Sorry, something went wrong.
No branches or pull requests
It is currently unspecified as to whether extraneous characters following
metric-name
should be ignored.We ignore extraneous characters found after a
server-timing-param-value
, so I'm inclined to do the same formetric-name
s.Example:
Note:
=
is not a legal token character.Options:
parsing should "keep going", yielding:
name=metric
duration=123.4
parsing should stop, yielding:
name=metric
duration=0
cc @yoavweiss
The text was updated successfully, but these errors were encountered: