-
Notifications
You must be signed in to change notification settings - Fork 101
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
GTFS download from URL: send a User-Agent #1562
Labels
enhancement
New feature request or improvement on an existing feature
status: Ready
An issue that is ready to be worked on.
Comments
4 tasks
Hi @derhuerst, as part of #1633, we're including the user-agent header in outgoing requests. To illustrate the expected formatting, this is an example, |
Sounds good! |
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
enhancement
New feature request or improvement on an existing feature
status: Ready
An issue that is ready to be worked on.
Describe the problem
As someone hosting (a) GTFS(s), I would like to see in my access logs which and how many requests come from the GTFS Validator, e.g. to gain insights into if/how the feed(s) are being validated, or to provide a more generous bandwidth quota.
Proposed solution
I propose to let the GTFS Validator send a
User-Agent
header with its requests.Alternatives you've considered
No response
Additional context
According to the
User-Agent
section in RFC 9110 (HTTP Semantics),User-Agent
shouldIt is also quite common to include a URL to the software's website or code repository, to let people contact the software's authors more conveniently.
The text was updated successfully, but these errors were encountered: