- Sort Score
- Result 10 results
- Languages All
Results 41 - 50 of 97 for work (0.13 sec)
-
docs/en/docs/tutorial/query-params.md
} ] } ``` As `needy` is a required parameter, you would need to set it in the URL: ``` http://127.0.0.1:8000/items/foo-item?needy=sooooneedy ``` ...this would work: ```JSON { "item_id": "foo-item", "needy": "sooooneedy" } ``` And of course, you can define some parameters as required, some as having a default value, and some entirely optional:
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Fri Oct 20 09:08:42 GMT 2023 - 5.1K bytes - Viewed (0) -
docs/en/docs/how-to/custom-request-and-route.md
And an `APIRoute` subclass to use that custom request class. ### Create a custom `GzipRequest` class !!! tip This is a toy example to demonstrate how it works, if you need Gzip support, you can use the provided [`GzipMiddleware`](../advanced/middleware.md#gzipmiddleware){.internal-link target=_blank}.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Sun Mar 31 23:52:53 GMT 2024 - 4.4K bytes - Viewed (0) -
docs/zh/docs/deployment/https.md
人们很容易认为 HTTPS 仅仅是“启用”或“未启用”的东西。 但实际情况比这复杂得多。 !!!提示 如果你很赶时间或不在乎,请继续阅读下一部分,下一部分会提供一个step-by-step的教程,告诉你怎么使用不同技术来把一切都配置好。 要从用户的视角**了解 HTTPS 的基础知识**,请查看 <a href="https://howhttps.works/" class="external-link" target="_blank">https://howhttps.works/</a>。 现在,从**开发人员的视角**,在了解 HTTPS 时需要记住以下几点: * 要使用 HTTPS,**服务器**需要拥有由**第三方**生成的**"证书(certificate)"**。 * 这些证书实际上是从第三方**获取**的,而不是“生成”的。 * 证书有**生命周期**。 * 它们会**过期**。
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Tue Jan 09 15:38:25 GMT 2024 - 10.6K bytes - Viewed (0) -
docs/pt/docs/deployment.md
Para aprender o básico de HTTPS, pela perspectiva de um consumidor, verifique <a href="https://howhttps.works/" class="external-link" target="_blank">https://howhttps.works/</a>. Agora, pela perspectiva de um desenvolvedor, aqui estão algumas coisas para se ter em mente enquanto se pensa sobre HTTPS:
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Aug 18 16:16:54 GMT 2022 - 16.8K bytes - Viewed (0) -
docs/de/docs/advanced/events.md
Da dieser Code ausgeführt wird, bevor die Anwendung **beginnt**, Requests entgegenzunehmen, und unmittelbar, nachdem sie die Bearbeitung von Requests **abgeschlossen hat**, deckt er die gesamte **Lebensdauer – „Lifespan“** – der Anwendung ab (das Wort „Lifespan“ wird gleich wichtig sein 😉).
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Sat Mar 30 20:30:59 GMT 2024 - 9.1K bytes - Viewed (0) -
docs/en/docs/tutorial/cors.md
## Wildcards It's also possible to declare the list as `"*"` (a "wildcard") to say that all are allowed. But that will only allow certain types of communication, excluding everything that involves credentials: Cookies, Authorization headers like those used with Bearer Tokens, etc. So, for everything to work correctly, it's better to specify explicitly the allowed origins.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Sun Nov 13 20:28:37 GMT 2022 - 5.1K bytes - Viewed (0) -
.github/DISCUSSION_TEMPLATE/questions.yml
Others - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Aug 03 15:59:41 GMT 2023 - 5.8K bytes - Viewed (1) -
docs/en/docs/tutorial/extra-models.md
All the data conversion, validation, documentation, etc. will still work as normally. That way, we can declare just the differences between the models (with plaintext `password`, with `hashed_password` and without password): === "Python 3.10+"
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 7.7K bytes - Viewed (1) -
docs/en/docs/deployment/index.md
There are several ways to do it depending on your specific use case and the tools that you use. You could **deploy a server** yourself using a combination of tools, you could use a **cloud service** that does part of the work for you, or other possible options. I will show you some of the main concepts you should probably keep in mind when deploying a **FastAPI** application (although most of it applies to any other type of web application).
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Jan 11 16:31:18 GMT 2024 - 1.2K bytes - Viewed (0) -
docs/en/docs/tutorial/security/simple-oauth2.md
OAuth2 specifies that when using the "password flow" (that we are using) the client/user must send a `username` and `password` fields as form data. And the spec says that the fields have to be named like that. So `user-name` or `email` wouldn't work. But don't worry, you can show it as you wish to your final users in the frontend. And your database models can use any other names you want.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 12.5K bytes - Viewed (0)