bug: v1.8 loaders have empty request.headers when called after action #4826
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.
This is a bug report:
yarn bug-report-test
Prior to Remix v1.8.0 the loader function when called subsequentially to a (POST) action would have the request's
headers
set. Since v1.8 this is not the case anymore.This is highlyt problematic. For example, if you have some high level session based cookie which is used to guard GET request in the page action (or a parent layout route); the authentication would fail every time the loaders data is retrieved subsequentially to a POST action.