pass auth headers to /csrf #16464
Merged
pass auth headers to /csrf #16464
Conversation
This file contains 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
aaazzam
requested review from
znicholasbrown,
cicdw,
desertaxle and
zzstoatzz
as code owners
github-actions
bot
added
bug
CodSpeed Performance ReportMerging #16464 will not alter performanceComparing Summary
|
cicdw
approved these changes
Dec 20, 2024
znicholasbrown
approved these changes
Dec 20, 2024
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.
in #16411, auth headers were passed to the central client-side API service which brokers all requests, except for the one to refresh the csrf token. With CSRF protection turned on, this means that PREFECT_SERVER_API_AUTH_STR showed a persistent login screen.
This PR does three things: