- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 1,748 for Code (0.02 sec)
-
docs/pt/docs/tutorial/response-status-code.md
# Código de status de resposta { #response-status-code } Da mesma forma que você pode especificar um modelo de resposta, você também pode declarar o código de status HTTP usado para a resposta com o parâmetro `status_code` em qualquer uma das *operações de rota*: * `@app.get()` * `@app.post()` * `@app.put()` * `@app.delete()` * etc. {* ../../docs_src/response_status_code/tutorial001_py39.py hl[6] *} /// note | NotaRegistered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Wed Dec 17 20:41:43 UTC 2025 - 4.4K bytes - Viewed (0) -
docs/de/docs/tutorial/response-status-code.md
# Response-Statuscode { #response-status-code } Genauso wie Sie ein Responsemodell angeben können, können Sie auch den HTTP-Statuscode für die <abbr title="Response – Antwort: Daten, die der Server zum anfragenden Client zurücksendet">Response</abbr> mit dem Parameter `status_code` in jeder der *Pfadoperationen* deklarieren: * `@app.get()` * `@app.post()` * `@app.put()` * `@app.delete()` * usw.Registered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Wed Dec 17 20:41:43 UTC 2025 - 4.9K bytes - Viewed (0) -
docs/ru/docs/tutorial/response-status-code.md
# Статус-код ответа { #response-status-code } Подобно тому, как вы можете задать модель/схему ответа, вы можете объявить HTTP статус-код, используемый для ответа, с помощью параметра `status_code` в любой из *операций пути*: * `@app.get()` * `@app.post()` * `@app.put()` * `@app.delete()` * и других. {* ../../docs_src/response_status_code/tutorial001_py39.py hl[6] *} /// note | ПримечаниеRegistered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Wed Dec 17 20:41:43 UTC 2025 - 7.1K bytes - Viewed (0) -
docs/es/docs/tutorial/response-status-code.md
# Código de Estado del Response { #response-status-code } De la misma manera que puedes especificar un modelo de response, también puedes declarar el código de estado HTTP usado para el response con el parámetro `status_code` en cualquiera de las *path operations*: * `@app.get()` * `@app.post()` * `@app.put()` * `@app.delete()` * etc. {* ../../docs_src/response_status_code/tutorial001_py39.py hl[6] *} /// note | NotaRegistered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Wed Dec 17 20:41:43 UTC 2025 - 4.4K bytes - Viewed (0) -
docs/en/docs/tutorial/response-status-code.md
# Response Status Code { #response-status-code } The same way you can specify a response model, you can also declare the HTTP status code used for the response with the parameter `status_code` in any of the *path operations*: * `@app.get()` * `@app.post()` * `@app.put()` * `@app.delete()` * etc. {* ../../docs_src/response_status_code/tutorial001_py39.py hl[6] *} /// noteRegistered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Wed Dec 17 20:41:43 UTC 2025 - 4K bytes - Viewed (0) -
docs/en/docs/how-to/authentication-error-status-code.md
Before FastAPI version `0.122.0`, when the integrated security utilities returned an error to the client after a failed authentication, they used the HTTP status code `403 Forbidden`.
Registered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Mon Nov 24 19:03:06 UTC 2025 - 1.3K bytes - Viewed (0) -
build-logic-commons/gradle-plugin/src/main/kotlin/gradlebuild.code-quality.gradle.kts
) nullawayEnabled.convention(false) } nullaway { // NullAway can use NullMarked instead, but for the adoption process it is more effective to assume that all gradle code is already annotated. // This way we can catch discrepancies in modules easier. We should make all packages NullMarked eventually too, but this is a separate task. annotatedPackages.add("org.gradle") } dependencies {Registered: Wed Dec 31 11:36:14 UTC 2025 - Last Modified: Wed Oct 01 11:57:43 UTC 2025 - 9.3K bytes - Viewed (0) -
docs/pt/docs/how-to/authentication-error-status-code.md
Mas, se por algum motivo seus clientes dependem do comportamento antigo, você pode voltar a ele sobrescrevendo o método `make_not_authenticated_error` nas suas classes de segurança. Por exemplo, você pode criar uma subclasse de `HTTPBearer` que retorne um erro `403 Forbidden` em vez do erro padrão `401 Unauthorized`:
Registered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Wed Dec 17 19:59:04 UTC 2025 - 1.3K bytes - Viewed (0) -
docs/en/docs/advanced/response-change-status-code.md
# Response - Change Status Code { #response-change-status-code } You probably read before that you can set a default [Response Status Code](../tutorial/response-status-code.md){.internal-link target=_blank}. But in some cases you need to return a different status code than the default. ## Use case { #use-case } For example, imagine that you want to return an HTTP status code of "OK" `200` by default.Registered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Wed Dec 17 20:41:43 UTC 2025 - 1.5K bytes - Viewed (0) -
docs/ru/docs/advanced/response-change-status-code.md
# Response - Изменение статус-кода { #response-change-status-code } Вы, вероятно, уже читали о том, что можно установить [статус-код ответа по умолчанию](../tutorial/response-status-code.md){.internal-link target=_blank}. Но в некоторых случаях нужно вернуть другой статус-код, отличный от значения по умолчанию. ## Пример использования { #use-case } Например, представьте, что вы хотите по умолчанию возвращать HTTP статус-код «OK» `200`.Registered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Wed Dec 17 20:41:43 UTC 2025 - 2.7K bytes - Viewed (0)