Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

馃摑 Update HTTPException details in docs/en/docs/tutorial/handling-errors.md #5418

Merged
merged 3 commits into from
Jan 15, 2024
Merged

馃摑 Update HTTPException details in docs/en/docs/tutorial/handling-errors.md #5418

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
1a56230
Update outdated info in handling-errors tutorial
papb Sep 22, 2022
f2d4477
Merge branch 'master' into patch-1
tiangolo Dec 16, 2022
34764b7
Merge branch 'master' into patch-1
tiangolo Jan 15, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
4 changes: 1 addition & 3 deletions docs/en/docs/tutorial/handling-errors.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -234,9 +234,7 @@ You will receive a response telling you that the data is invalid containing the

And **FastAPI**'s `HTTPException` error class inherits from Starlette's `HTTPException` error class.

The only difference, is that **FastAPI**'s `HTTPException` allows you to add headers to be included in the response.

This is needed/used internally for OAuth 2.0 and some security utilities.
The only difference is that **FastAPI**'s `HTTPException` accepts any JSON-able data for the `detail` field, while Starlette's `HTTPException` only accepts strings for it.

So, you can keep raising **FastAPI**'s `HTTPException` as normally in your code.

Expand Down