From 3e80032104aec6c31c4d23ef5938c978fc2ab38a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Sebasti=C3=A1n=20Ram=C3=ADrez?= Date: Mon, 24 Nov 2025 19:33:38 +0100 Subject: [PATCH] =?UTF-8?q?=F0=9F=93=9D=20Fix=20docs=20include?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- docs/en/docs/how-to/authentication-error-status-code.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/docs/how-to/authentication-error-status-code.md b/docs/en/docs/how-to/authentication-error-status-code.md index 093d2ae70..f9433e5dd 100644 --- a/docs/en/docs/how-to/authentication-error-status-code.md +++ b/docs/en/docs/how-to/authentication-error-status-code.md @@ -8,7 +8,7 @@ But if for some reason your clients depend on the old behavior, you can revert t For example, you can create a subclass of `HTTPBearer` that returns a `403 Forbidden` error instead of the default `401 Unauthorized` error: -{* ../../docs_src/authentication_error_status_code/tutorial001_py39.py hl[9:13] *} +{* ../../docs_src/authentication_error_status_code/tutorial001_an_py39.py hl[9:13] *} /// tip