fix: allow Debugbar to load with strict form request validation enabled#2032
Merged
Conversation
8e0a955 to
7c875e0
Compare
Member
|
Thanks! |
Member
|
Not sure why they are named differently though :P |
This was referenced Apr 20, 2026
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.
Laravel v13.4.0 introduced a new feature: strict mode for form request validation.
When enabled globally, this causes Debugbar assets to not load because the
hashandmtimeparameters are missing from the form request validation.As a result, these requests will return a 302 status response:
You can verify this by adding the following to
app/Providers/AppServiceProvider.php:This PR fixes the issue by adding
hashandmtimeas optional parameters to theAssetRequestvalidation rules.