mirror of https://github.com/tiangolo/fastapi.git
✏️ Fix links and add missing permalink in docs (#14217)
* Fix link url to match link text * Add missing permalink in `behind-a-proxy.md` * Fix link in `advanced-dependencies.md`
This commit is contained in:
parent
9e362d9f6e
commit
42930fe600
|
|
@ -144,7 +144,7 @@ This was changed in version 0.110.0 to fix unhandled memory consumption from for
|
||||||
|
|
||||||
### Background Tasks and Dependencies with `yield`, Technical Details { #background-tasks-and-dependencies-with-yield-technical-details }
|
### Background Tasks and Dependencies with `yield`, Technical Details { #background-tasks-and-dependencies-with-yield-technical-details }
|
||||||
|
|
||||||
Before FastAPI 0.106.0, raising exceptions after `yield` was not possible, the exit code in dependencies with `yield` was executed *after* the response was sent, so [Exception Handlers](../handling-errors.md#install-custom-exception-handlers){.internal-link target=_blank} would have already run.
|
Before FastAPI 0.106.0, raising exceptions after `yield` was not possible, the exit code in dependencies with `yield` was executed *after* the response was sent, so [Exception Handlers](../tutorial/handling-errors.md#install-custom-exception-handlers){.internal-link target=_blank} would have already run.
|
||||||
|
|
||||||
This was designed this way mainly to allow using the same objects "yielded" by dependencies inside of background tasks, because the exit code would be executed after the background tasks were finished.
|
This was designed this way mainly to allow using the same objects "yielded" by dependencies inside of background tasks, because the exit code would be executed after the background tasks were finished.
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -64,7 +64,7 @@ If you want to learn more about HTTPS, check the guide [About HTTPS](../deployme
|
||||||
|
|
||||||
///
|
///
|
||||||
|
|
||||||
### How Proxy Forwarded Headers Work
|
### How Proxy Forwarded Headers Work { #how-proxy-forwarded-headers-work }
|
||||||
|
|
||||||
Here's a visual representation of how the **proxy** adds forwarded headers between the client and the **application server**:
|
Here's a visual representation of how the **proxy** adds forwarded headers between the client and the **application server**:
|
||||||
|
|
||||||
|
|
@ -228,7 +228,7 @@ Passing the `root_path` to `FastAPI` would be the equivalent of passing the `--r
|
||||||
|
|
||||||
Keep in mind that the server (Uvicorn) won't use that `root_path` for anything else than passing it to the app.
|
Keep in mind that the server (Uvicorn) won't use that `root_path` for anything else than passing it to the app.
|
||||||
|
|
||||||
But if you go with your browser to <a href="http://127.0.0.1:8000" class="external-link" target="_blank">http://127.0.0.1:8000/app</a> you will see the normal response:
|
But if you go with your browser to <a href="http://127.0.0.1:8000/app" class="external-link" target="_blank">http://127.0.0.1:8000/app</a> you will see the normal response:
|
||||||
|
|
||||||
```JSON
|
```JSON
|
||||||
{
|
{
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue