В этом разделе посмотрим, как использовать другие middleware.

## Добавление ASGI middleware { #adding-asgi-middlewares }

Так как **FastAPI** основан на Starlette и реализует спецификацию <abbr title="Asynchronous Server Gateway Interface – Асинхронный шлюзовой интерфейс сервера">ASGI</abbr>, вы можете использовать любое ASGI middleware.

Sie können das verwenden, um ein `dict` zu erstellen, das nur die (im <abbr title="Request – Anfrage: Daten, die der Client zum Server sendet">Request</abbr>) gesendeten Daten enthält, ohne Defaultwerte:

{* ../../docs_src/body_updates/tutorial002_py310.py hl[32] *}

### Pydantics `update`-Parameter verwenden { #using-pydantics-update-parameter }

  }

  /**
   * Configures the given map maker to use weak keys, if possible; does nothing otherwise (i.e., in
   * GWT). This is sometimes acceptable, when only server-side code could generate enough volume
   * that reclamation becomes important.
   */
  @J2ktIncompatible
  static MapMaker tryWeakKeys(MapMaker mapMaker) {
    return mapMaker.weakKeys();
  }

### En un Servidor Remoto { #in-a-remote-server }

<font color="#4E9A06">INFO</font>:     Started reloader process [<font color="#34E2E2"><b>2265862</b></font>] using <font color="#34E2E2"><b>WatchFiles</b></font>
<font color="#4E9A06">INFO</font>:     Started server process [<font color="#06989A">2265873</font>]
<font color="#4E9A06">INFO</font>:     Waiting for application startup.
<font color="#4E9A06">INFO</font>:     Application startup complete.
```

</div>

// the handler should ensure to remove these keys before sending them to the object layer.
// Currently these keys are:
//   - X-Amz-Server-Side-Encryption-Customer-Key
//   - X-Amz-Copy-Source-Server-Side-Encryption-Customer-Key
func (api objectAPIHandlers) CopyObjectHandler(w http.ResponseWriter, r *http.Request) {
	ctx := newContext(r, w, "CopyObject")

    }

    @Test
    @DisplayName("Test with various pipe name formats")
    void testVariousPipeNameFormats() {
        // Test various pipe name formats
        String[] pipeNames =
                { "\\\\server\\PIPE\\testpipe", "\\PIPE\\LANMAN", "\\PIPE\\srvsvc", "\\PIPE\\wkssvc", "PIPE\\test", "testpipe" };

        for (String pipeName : pipeNames) {
            // Act

                /* When DFS is in action all request paths are
                 * full UNC paths minus the first backslash like
                 *   \server\share\path\to\file
                 * as opposed to normally
                 *   \path\to\file
                 */
                request.flags2 = SmbConstants.FLAGS2_RESOLVE_PATHS_IN_DFS;

### Modell für Ausgabe-Responsedaten { #model-for-output-response-data }

Wenn Sie mit der Dokumentation interagieren und die <abbr title="Response – Antwort: Daten, die der Server zum anfragenden Client zurücksendet">Response</abbr> überprüfen, enthält die JSON-Response den Defaultwert (`null`), obwohl der Code nichts in eines der `description`-Felder geschrieben hat:

<div class="screenshot">

	configFiles := []string{
		getConfigFile(),
		getConfigFile() + ".deprecated",
		configFile,
	}

	newServerCfg := func() (config.Config, error) {
		// Initialize server config.
		srvCfg := newServerConfig()

		return srvCfg, saveServerConfig(ctx, objAPI, srvCfg)
	}

	var data []byte
	var err error

	cfg := &serverConfigV33{}
	for _, cfgFile := range configFiles {