rate.limit.enabled=false
# Maximum number of requests allowed per window.
rate.limit.requests.per.window=100
# Window size in milliseconds.
rate.limit.window.ms=60000
# Duration in milliseconds to block IP when limit exceeded.
rate.limit.block.duration.ms=300000
# Retry-After header value in seconds.
rate.limit.retry.after.seconds=60
# Comma-separated list of whitelisted IPs (e.g., 127.0.0.1,::1).

Vous pouvez démarrer FastAPI CLI avec l'option de CLI `--forwarded-allow-ips` et fournir les adresses IP à considérer comme fiables pour lire ces en‑têtes transférés.

Si vous la définissez à `--forwarded-allow-ips="*"`, elle fera confiance à toutes les IP entrantes.

Se você definir como `--forwarded-allow-ips="*"`, ele confiará em todos os IPs de entrada.

Se o seu **servidor** estiver atrás de um **proxy** confiável e somente o proxy falar com ele, isso fará com que ele aceite seja qual for o IP desse **proxy**.

<div class="termy">

```console

nittedal.no
niyodogawa.kochi.jp
nj.us
njs.jelastic.vps-host.net
nl
nl-ams-1.baremetal.scw.cloud
nl.ca
nl.eu.org
nl.no
nm.cn
nm.us
no
no-ip.biz
no-ip.ca
no-ip.co.uk
no-ip.info
no-ip.net
no-ip.org
no.eu.org
no.it
nobeoka.miyazaki.jp
noboribetsu.hokkaido.jp
nobushi.jp
noda.chiba.jp
noda.iwate.jp
nodes.k8s.fr-par.scw.cloud

      "method": "get"
    },
    "response": {
      "bytes": 1070000,
      "status_code": 200
    },
    "version": "1.1"
  },
  "message": "GET /search HTTP/1.1 200 1070000",
  "source": {
    "ip": "192.168.0.1"
  },
  "user": {
    "id": "user"
  }

- The kubelet, when using `--cloud-provider=external` can use the `--node-ip` flag with one of the unspecified addresses 0.0.0.0 or ::, to create the Node with the IP of the default gateway of the corresponding IP family and then delegating the responsibility to the external cloud provider. This solves the bootstrap problems of out of tree cloud providers that are deployed as Pods within the...

- Kubelet now cleans up the Node's cloud node IP annotation correctly if you
  stop using `--node-ip`. (In particular, this fixes the problem where people who
  were unnecessarily using `--node-ip` with an external cloud provider in 1.23,
  and then running into problems with 1.24, could not fix the problem by just
  removing the unnecessary `--node-ip` from the kubelet arguments, because

Puedes iniciar FastAPI CLI con la *Opción de CLI* `--forwarded-allow-ips` y pasar las direcciones IP que deberían ser confiables para leer esos headers reenviados.

Si lo estableces a `--forwarded-allow-ips="*"`, confiaría en todas las IPs entrantes.

Si tu **server** está detrás de un **proxy** confiable y solo el proxy le habla, esto haría que acepte cualquiera que sea la IP de ese **proxy**.

<div class="termy">

```console

Wenn Sie es auf `--forwarded-allow-ips="*"` setzen, würde es allen eingehenden IPs vertrauen.

Wenn Ihr **Server** hinter einem vertrauenswürdigen **Proxy** sitzt und nur der Proxy mit ihm spricht, würde dies dazu führen, dass er die IP dieses **Proxys** akzeptiert, was auch immer sie ist.

Mais il existe des cas spécifiques où il est utile d'obtenir l'objet `Request`.

## Utiliser l'objet `Request` directement { #use-the-request-object-directly }

Imaginons que vous souhaitiez obtenir l'adresse IP/l'hôte du client dans votre fonction de chemin d'accès.

Pour cela, vous devez accéder directement à la requête.

{* ../../docs_src/using_request_directly/tutorial001_py310.py hl[1,7:8] *}