Store previous locations for Inertia visits - #888
Open
drewmt wants to merge 1 commit into
Open
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
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.
Summary
Inertia page visits include the
X-Requested-With: XMLHttpRequestheader, so Laravel's session middleware intentionally skips updating the previous URL and route. As a result, session navigation history can remain stuck on the last full-page visit.This change stores the current URL and route for Inertia GET visits that Laravel skips, while preserving the existing exclusions for regular AJAX requests, prefetches, precognitive requests, and non-GET requests. Route history is detected as an optional session capability so Laravel 11 remains supported.
Fixes #886.
User impact
Applications can reliably use
previousUrl()/previousUri()and, on supported Laravel versions,previousRoute()after client-side Inertia navigation. Existing non-navigation requests keep their current behavior.Validation
3.ximplementation before the fix.composer validate --strictandcomposer auditpass with current dependencies.