-
Notifications
You must be signed in to change notification settings - Fork 889
New issue
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
correct exporter user-agent example #3052
Conversation
While this section about a User-Agent references RFC7231[1] for format, the example provided includes spaces in the product identifier. The product identifier comes in the form of a token, defined in RFC7230[2]. Including spaces will throw off most existing user-agent parsing. [1] https://datatracker.ietf.org/doc/html/rfc7231#section-5.5.3 [2] https://datatracker.ietf.org/doc/html/rfc7230#section-3.2.6
Thank you! Please also add an entry in |
cc @codeboten |
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
I am unclear on what change I should make: remove the changelog entry or move it to a different section? If a different section, which section? OpenTelemetry Protocol because this is about OTLP exporters? |
@robbkidd Oh, I meant removing the entry from the Changelog basically. On a second though, we want to be explicit to SIGs about updating their user agents, so leets keep keep the entry. |
Changes
Removes spaces from the example exporter User-Agent string to conform to header field value component definition.
While this section about a User-Agent references RFC7231 for format, the example provided includes spaces in the
product
identifier. The format forproduct
is as atoken
, defined in RFC7230, which does not include space in the set of valid characters. Including spaces here will throw off most existing user-agent parsing.Related issues: example added in #2684