Fix #22862 - change the httpclient user-agent to be valid spec-wise #22882
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Per https://datatracker.ietf.org/doc/html/rfc9110#name-user-agent a User-Agent is defined as follows:
Where
In this case,
token
is defined in RFC 7230 - https://datatracker.ietf.org/doc/html/rfc7230#section-3.2.6:or, in the original RFC 2616 - https://datatracker.ietf.org/doc/html/rfc2616#section-2.2 (next page):
which means that a
token
cannot have whitespace. Not sure if this should be in the breaking changelog section - theoretically, some clients might've relied on the old Nim user-agent?For some extra info, some other languages seem to have adopted the same hyphen user agent to specify the language + module, e.g.:
Python-urllib/<version>
)Fixes #22862.