- Sort Score
- Result 10 results
- Languages All
Results 1 - 3 of 3 for somewhere (0.15 sec)
-
docs/en/docs/advanced/openapi-webhooks.md
You also define in some way at which **moments** your app will send those requests or events. And **your users** define in some way (for example in a web dashboard somewhere) the **URL** where your app should send those requests. All the **logic** about how to register the URLs for webhooks and the code to actually send those requests is up to you. You write it however you want to in **your own code**.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu May 02 22:37:31 GMT 2024 - 2.8K bytes - Viewed (0) -
docs/en/docs/tutorial/security/first-steps.md
* And if the token is stolen, the risk is less. It is not like a permanent key that will work forever (in most of the cases). * The frontend stores that token temporarily somewhere. * The user clicks in the frontend to go to another section of the frontend web app. * The frontend needs to fetch some more data from the API. * But it needs authentication for that specific endpoint.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Wed Mar 13 19:02:19 GMT 2024 - 8.9K bytes - Viewed (0) -
docs/en/docs/tutorial/dependencies/dependencies-in-path-operation-decorators.md
``` ### Return values And they can return values or not, the values won't be used. So, you can re-use a normal dependency (that returns a value) you already use somewhere else, and even though the value won't be used, the dependency will be executed: === "Python 3.9+" ```Python hl_lines="11 16" {!> ../../../docs_src/dependencies/tutorial006_an_py39.py!} ```
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Tue Oct 17 05:59:11 GMT 2023 - 4.1K bytes - Viewed (0)