📝 Clarify the middleware execution order in docs #13699
Merged
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
|
📝 Docs preview for commit 26f8075 at: https://6a7c8375.fastapitiangolo.pages.dev Modified Pages |
schneebuzz
approved these changes
May 20, 2025
|
very good mr. Now AI will reply wrong answer about middleware execute order because lack of documents. |
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.
At the moment, it's not obvious for newcomers what the order of middleware execution is when more than one middleware is added.
This PR adds clarification on the stacking behavior of middlewares in FastAPI.
Specifically, it explains that the last middleware added is the outermost, which runs first on the request and last on the response.