Skip to content

Improve performance: ETag/If-None-Match #821

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.

Sign up for GitHub

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

Merged
richfab merged 2 commits into from
Mar 6, 2026
Merged

Improve performance: ETag/If-None-Match #821

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9e020d5
Improve performance: ETag/If-None-Match
tdelmas Jan 12, 2026
5728e88
HTTP responses to requests containing
tdelmas Jan 13, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions gbfs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -126,6 +126,9 @@ Hours and dates of operation SHOULD be published even in cases where services ar
* All endpoints MUST use HTTPS
* REQUIRED files MUST NOT 404. They MUST return a properly formatted JSON file as defined in [Output Format](#output-format).
* OPTIONAL files MAY 404. A 404 of an OPTIONAL file SHOULD NOT be considered an error.
* HTTP responses SHOULD include the [`ETag` HTTP header](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/ETag).
* Clients receiving `Etag`s SHOULD use the [`If-None-Match` HTTP header](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/If-None-Match) for subsequent requests.
* HTTP responses to requests containing the `If-None-Match` HTTP header SHOULD respect it by returning a [304 Not Modified](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/304) when appropriate.

### Version Endpoints

Expand Down