* Die Informationen über die angeforderte **spezifische Domain** befinden sich in den **HTTP-Daten**.
* Die **HTTPS-Zertifikate** „zertifizieren“ eine **bestimmte Domain**, aber das Protokoll und die Verschlüsselung erfolgen auf TCP-Ebene, **ohne zu wissen**, um welche Domain es sich handelt.
* **Standardmäßig** bedeutet das, dass Sie nur **ein HTTPS-Zertifikat pro IP-Adresse** haben können.

## Instalar `websockets` { #install-websockets }

Asegúrate de crear un [entorno virtual](../virtual-environments.md), activarlo e instalar `websockets` (un paquete de Python que facilita usar el protocolo "WebSocket"):

<div class="termy">

```console
$ pip install websockets

---> 100%
```

</div>

## Cliente WebSockets { #websockets-client }

### En producción { #in-production }

    response: Response,
    expectedHost: String,
  ) {
    assertThat(response.code).isEqualTo(200)
    assertThat(response.request.url.host).isEqualTo(expectedHost)
    assertThat(response.protocol).isEqualTo(Protocol.HTTP_2)
    response.body.close()
  }

 * [Stetho](https://github.com/facebook/stetho): Stetho is a debug bridge for Android applications.

 */
package jcifs;

import java.util.EnumSet;
import java.util.Set;

import jcifs.internal.smb2.Smb2Constants;

/**
 * Enumeration of SMB protocol dialect versions supported by JCIFS.
 * This includes legacy SMB1/CIFS as well as modern SMB2/SMB3 dialects.
 *
 * @author mbechler
 */
public enum DialectVersion {

    /**
     * Legacy SMB1/CIFS
     */

heritage: Helm spec: type: ClusterIP ports: - name: http port: 9001 protocol: TCP targetPort: 9001 selector: app: minio release: chart-1640120023 --- # Source: minio/templates/service.yaml apiVersion: v1 kind: Service metadata: name: chart-1640120023-minio namespace: "minio" labels: app: minio chart: minio-3.4.2 release: chart-1640120023 heritage: Helm monitoring: "true" spec: type: ClusterIP ports: - name: http port: 9000 protocol: TCP targetPort: 9000 selector: app: minio release: chart-1640120023...

import jcifs.internal.util.SMBUtil;

/**
 * SMB1 COM_WRITE command implementation.
 *
 * This command writes data to an open file on the server.
 * It's the basic write operation in the SMB1 protocol.
 */
public class SmbComWrite extends ServerMessageBlock {

    private int fid, count, offset, remaining, off;
    private byte[] b;

    /**
     * Constructs an empty write request.
     *

 * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
 */

package jcifs.smb1.smb1;

/**
 * Interface defining DOS error codes and their mappings to NT status codes for SMB1 protocol.
 * Provides lookup tables for converting between DOS and NT error representations.
 */
public interface DosError {

    /**
     * Mapping table from DOS error codes to NT status codes.

Isso não é uma limitação do **FastAPI**, é parte do protocolo HTTP.

///

## Upload de Arquivo Opcional { #optional-file-upload }

Você pode tornar um arquivo opcional usando anotações de tipo padrão e definindo um valor padrão de `None`:

{* ../../docs_src/server_sent_events/tutorial004_py310.py hl[25,27,31] *}

## SSE mit POST { #sse-with-post }

SSE funktioniert mit **jedem HTTP-Method**, nicht nur mit `GET`.

Das ist nützlich für Protokolle wie [MCP](https://modelcontextprotocol.io), die SSE über `POST` streamen:

{* ../../docs_src/server_sent_events/tutorial005_py310.py hl[14] *}

## Technische Details { #technical-details }