* Validate host name
     */
    private boolean isValidHost(String host) {
        if (host == null || host.isEmpty()) {
            return false;
        }

        // Check for valid hostname or IP address
        // Simple validation - can be enhanced
        if (host.length() > 255) {
            return false;
        }

        // Check for invalid characters

    
    public static class WitnessIPAddress {
        private final InetAddress address;
        private final int flags;
        
        public static final int IPV4 = 0x01;
        public static final int IPV6 = 0x02;
        
        public WitnessIPAddress(InetAddress address) {
            this.address = address;
            this.flags = address.getAddress().length == 4 ? IPV4 : IPV6;
        }
        

    protected int netbiosLocalPort = 0;
    /** Local address for NetBIOS communications */
    protected InetAddress netbiosLocalAddress;
    /** Path to lmhosts file for NetBIOS name resolution */
    protected String lmhostsFilename;
    /** Array of WINS server addresses for NetBIOS name resolution */
    protected InetAddress[] winsServer = {};
    /** Broadcast address for NetBIOS name resolution */

Então, crie um arquivo `traefik.toml` com:

```TOML hl_lines="3"
[entryPoints]
  [entryPoints.http]
    address = ":9999"

[providers]
  [providers.file]
    filename = "routes.toml"
```

Isso diz ao Traefik para escutar na porta 9999 e usar outro arquivo `routes.toml`.

/// tip | Dica

* kubelets that specify `--cloud-provider` now only report addresses in Node status as determined by the cloud provider ([#65594](https://github.com/kubernetes/kubernetes/pull/65594), [@liggitt](https://github.com/liggitt))
   * kubelet serving certificate rotation now reacts to changes in reported node addresses, and will request certificates for addresses set by an external cloud provider

- Added warnings to the Services API. Kubernetes now warns for Services in the case of:
  - IPv4 addresses with leading zeros
  - IPv6 address in non-canonical format (RFC 5952) ([#114505](https://github.com/kubernetes/kubernetes/pull/114505), [@aojea](https://github.com/aojea))

- The kube-apiserver ability to serve on an insecure port, deprecated since v1.10, has been removed. The insecure address flags `--address` and `--insecure-bind-address` have no effect in kube-apiserver and will be removed in v1.24. The insecure port flags `--port` and `--insecure-port` may only be set to 0 and will be removed in v1.24. ([#95856](https://github.com/kubernetes/kubernetes/pull/95856),...

* Only use the first IP address got from instance metadata. This is because Azure CNI would set up a list of IP addresses in instance metadata, while only the first one is the Node's IP. ([#71736](https://github.com/kubernetes/kubernetes/pull/71736), [@feiskyer](https://github.com/feiskyer))

### Choosing between application and network interceptors

Each interceptor chain has relative merits.

**Application interceptors**

## Dépendances facultatives

Utilisées par Pydantic:

* <a href="https://github.com/JoshData/python-email-validator" target="_blank"><code>email-validator</code></a> - pour la validation des adresses email.

Utilisées par Starlette :

* <a href="https://requests.readthedocs.io" target="_blank"><code>requests</code></a> - Obligatoire si vous souhaitez utiliser `TestClient`.