Fix an issue: HX-Location and HX-Redirect headers ignored during history restoration. #3433
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.
Description
This PR fixes an issue where
HX-LocationandHX-Redirectheaders were not being processed during history restoration when users navigate using the browser's back button. This causes problems if your application has authentication pages and controls invalid access using redirects.Corresponding issue: #3432
Testing
I used updated code for my work which is not open source. I created a login form with htmx and checked the browser's back button behavior manually.
Checklist
masterfor website changes,devforsource changes)
approved via an issue
npm run test) and verified that it succeeded