Support for ETag and If-Not-Modified in GBFS updater #6963
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.
Summary
This PR adds support for keeping ETag header values from GBFS datasource responses, and passing them to subsequent requests, in order for the server to respond with 304 Not Modified when the content hasn't changed.
If the responses don't have an ETag header, there is no change in behavior.
Issue
Closes #6927
Unit tests
All existing tests pass. No additional tests added as changes are mostly based around the http client. The ETag/if-not-modified behavior has been manually tested against Entur's gbfs aggregator.