Repository navigation
fix(google_fastly_waf): Do not serve GET cached responses on OPTIONS requests - #504
Merged
Merged
Conversation
GET cached responses on OPTIONS requestsGET cached responses on OPTIONS requests
Contributor
Release plan
|
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
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.
Description
Since we migrated to Fastly, we cannot navigate the Remote Settings public data from the Admin UI.
Because OPTIONS requests are served cached GET responses.
This PR sends anything but GET/HEAD/FASTLYPURGE to the origins.
Who it affects in webservices-infra
Related Tickets & Documents