Repository navigation
Conversation
The Eloquent saved/deleted listeners collecting cache tags were only registered by the REST controller, so a GraphQL mutation changed data without purging anything and cached GET responses stayed stale. The GraphQL entrypoint now registers the same listeners.
VarnishPurger was built without the configured api-platform.http_cache.invalidation.max_header_length, unlike the xkey and Souin purgers, so it always used its 8000 default and could send BAN headers larger than the cache server accepts.
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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.
With HTTP cache invalidation enabled on Laravel, the
eloquent.saved/eloquent.deletedlisteners that collect the IRIs to purge were only registered by the REST controller: a GraphQL mutation never purged anything, so REST clients kept getting the stale item and collection. The GraphQL entrypoint now registers them too. The Varnish purger also ignoredhttp_cache.invalidation.max_header_length, which the other purgers receive.Tests:
src/Laravel/Tests/GraphQlPurgerTest.php(new) andPurgerTest.