Explicitly request no-cache to discourage WP Cloud from edge caching CORS proxy results #1930
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.
Motivation for the change, related issues
This PR attempts to disable WP Cloud edge caching of CORS proxy responses.
Closes #1920
Implementation details
This PR updates the CORS proxy to always include a
Cache-Control: no-cache
header with normal proxy responses.Testing Instructions (or ideally a Blueprint)
cors-proxy-config.php
that defines a truthyPLAYGROUND_CORS_PROXY_DISABLE_RATE_LIMIT
constant. This disables rate-limiting checks which are irrelevant to this change.php -S localhost:7777
Cache-Control: no-cache
header