Improve performance: ETag/If-None-Match#821
Merged
richfab merged 2 commits intoMobilityData:masterfrom Mar 6, 2026
Merged
Conversation
Signed-off-by: tdelmas <tdelmas@users.noreply.github.com>
mplsmitch
suggested changes
Jan 12, 2026
3 tasks
mplsmitch
approved these changes
Mar 2, 2026
Contributor
|
Thanks @tdelmas for this proposal, which follows the discussions held at the Mobility Data Summit on Oct 2024. We deem that there is no need for a vote because this change is a best practice on the web, not specific to GBFS. I'll merge the proposal into master now (v3.1-RC2). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
What problem does your proposal solve? Please begin with the relevant issue number. If there is no existing issue, please also describe alternative solutions you have considered.
Allow consumers to easily cache anwsers with minimal burden on producers (Fix #708)
What is the proposal?
The HTTP ETag/If-None-Match mechanism
Is this a breaking change?
Not a breaking change, as the "SHOULD" requirement allow some flexibility both for producers and consumers.