Repository navigation
Conversation
soyuka
force-pushed
the
fix/laravel-validate-header-parameters
branch
from
October 19, 2026 12:17
4031d05 to
605610d
Compare
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
1 participant
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.
ParameterValidatorProvidercollected constraints of every parameter but validated them against$request->query->all(), so header constraints were checked against the query string: a required header was rejected even when sent, and satisfied by a same-named query parameter.Header parameters are now validated against their resolved value. Query and headers run as two validator passes, so a header and a query parameter with the same name don't collide (query errors are reported first).