- Sort Score
- Result 10 results
- Languages All
Results 11 - 20 of 21 for browser (0.19 sec)
-
docs/de/docs/tutorial/middleware.md
werden können. <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers" class="external-link" target="_blank">Verwenden Sie dafür das Präfix 'X-'</a>. Wenn Sie jedoch benutzerdefinierte Header haben, die ein Client in einem Browser sehen soll, müssen Sie sie zu Ihrer CORS-Konfigurationen ([CORS (Cross-Origin Resource Sharing)](cors.md){.internal-link target=_blank}) hinzufügen, indem Sie den Parameter `expose_headers` verwenden, der in der <a href="https://www.starlette.io/...
Registered: Mon Jun 17 08:32:26 UTC 2024 - Last Modified: Tue Jan 23 11:26:59 UTC 2024 - 3.4K bytes - Viewed (0) -
docs/en/docs/tutorial/middleware.md
that custom proprietary headers can be added <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers" class="external-link" target="_blank">using the 'X-' prefix</a>. But if you have custom headers that you want a client in a browser to be able to see, you need to add them to your CORS configurations ([CORS (Cross-Origin Resource Sharing)](cors.md){.internal-link target=_blank}) using the parameter `expose_headers` documented in <a href="https://www.starlette.io/middleware/#corsmiddleware"...
Registered: Mon Jun 17 08:32:26 UTC 2024 - Last Modified: Thu Jan 11 16:31:18 UTC 2024 - 2.9K bytes - Viewed (0) -
docs/en/docs/advanced/sub-applications.md
<img src="/img/tutorial/sub-applications/image02.png"> If you try interacting with any of the two user interfaces, they will work correctly, because the browser will be able to talk to each specific app or sub-app. ### Technical Details: `root_path`
Registered: Mon Jun 17 08:32:26 UTC 2024 - Last Modified: Thu Apr 18 19:53:19 UTC 2024 - 2.9K bytes - Viewed (0) -
docs/pt/docs/tutorial/security/first-steps.md
Então, vamos rever de um ponto de vista simplificado: * O usuário digita o `username` e a `senha` no frontend e aperta `Enter`. * O frontend (rodando no browser do usuário) manda o `username` e a `senha` para uma URL específica na sua API (declarada com `tokenUrl="token"`). * A API checa aquele `username` e `senha`, e responde com um "token" (nós não implementamos nada disso ainda).
Registered: Mon Jun 17 08:32:26 UTC 2024 - Last Modified: Thu Apr 18 19:53:19 UTC 2024 - 8.3K bytes - Viewed (0) -
docs/en/docs/tutorial/security/first-steps.md
So, let's review it from that simplified point of view: * The user types the `username` and `password` in the frontend, and hits `Enter`. * The frontend (running in the user's browser) sends that `username` and `password` to a specific URL in our API (declared with `tokenUrl="token"`). * The API checks that `username` and `password`, and responds with a "token" (we haven't implemented any of this yet).
Registered: Mon Jun 17 08:32:26 UTC 2024 - Last Modified: Mon Jun 03 01:48:20 UTC 2024 - 9.1K bytes - Viewed (0) -
docs/de/docs/tutorial/body.md
# Requestbody Wenn Sie Daten von einem <abbr title="Client: Eine Software, die sich mit einem Server verbindet.">Client</abbr> (sagen wir, einem Browser) zu Ihrer API senden, dann senden Sie diese als einen **Requestbody** (Deutsch: Anfragekörper). Ein **Request**body sind Daten, die vom Client zu Ihrer API gesendet werden. Ein **Response**body (Deutsch: Antwortkörper) sind Daten, die Ihre API zum Client sendet.
Registered: Mon Jun 17 08:32:26 UTC 2024 - Last Modified: Fri Mar 22 01:42:11 UTC 2024 - 8.1K bytes - Viewed (0) -
docs/de/docs/tutorial/query-params.md
```Python hl_lines="6-7" {!../../../docs_src/query_params/tutorial005.py!} ``` Hier ist `needy` ein erforderlicher Query-Parameter vom Typ `str`. Wenn Sie in Ihrem Browser eine URL wie: ``` http://127.0.0.1:8000/items/foo-item ``` ... öffnen, ohne den benötigten Parameter `needy`, dann erhalten Sie einen Fehler wie den folgenden: ```JSON { "detail": [
Registered: Mon Jun 17 08:32:26 UTC 2024 - Last Modified: Thu Jan 25 14:53:41 UTC 2024 - 5.6K bytes - Viewed (0) -
docs/en/docs/tutorial/body.md
# Request Body When you need to send data from a client (let's say, a browser) to your API, you send it as a **request body**. A **request** body is data sent by the client to your API. A **response** body is the data your API sends to the client. Your API almost always has to send a **response** body. But clients don't necessarily need to send **request** bodies all the time.
Registered: Mon Jun 17 08:32:26 UTC 2024 - Last Modified: Fri Mar 22 01:42:11 UTC 2024 - 7.3K bytes - Viewed (0) -
docs/en/docs/tutorial/handling-errors.md
# Handling Errors There are many situations in which you need to notify an error to a client that is using your API. This client could be a browser with a frontend, a code from someone else, an IoT device, etc. You could need to tell the client that: * The client doesn't have enough privileges for that operation. * The client doesn't have access to that resource. * The item the client was trying to access doesn't exist. * etc.
Registered: Mon Jun 17 08:32:26 UTC 2024 - Last Modified: Sat May 18 23:43:13 UTC 2024 - 9.1K bytes - Viewed (0) -
docs/en/docs/features.md
Registered: Mon Jun 17 08:32:26 UTC 2024 - Last Modified: Thu May 02 22:37:31 UTC 2024 - 9.3K bytes - Viewed (0)