[6.x] Serve HEAD requests from the static cache - #15168
Merged
jasonvarga merged 1 commit intoAug 11, 2026
Merged
Conversation
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
2 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.
The static caching middleware only ever reads the cache for GET requests, so a HEAD request to a page that's already cached runs the whole render pipeline anyway. Symfony then throws the body away when it prepares the response, so all that work is wasted. Uptime monitors, crawlers and link checkers tend to use HEAD, and on a half measure site they end up an order of magnitude slower than the equivalent GET.
Laravel routes HEAD requests through the matching GET route, and the cacher keys pages by URL, so a HEAD request can just be served the response that GET already cached. This lets
canBeCached()through for HEAD as well.Writes are untouched.
shouldBeCached()still only allows GET, so a HEAD miss renders as before without populating the cache with an emptied response.Fixes #15165