So, the dependency function will be executed **around** the *path operation
                **function***.
            * `"request"`: start the dependency before the *path operation function*
                that handles the request (similar to when using `"function"`), but end
                **after** the response is sent back to the client. So, the dependency

Para isso, use o padrão Python `typing.List` (ou simplesmente `list` no Python 3.9 e superior):

{* ../../docs_src/extra_models/tutorial004_py39.py hl[18] *}

## Resposta com `dict` arbitrário { #response-with-arbitrary-dict }

Você também pode declarar uma resposta usando um simples `dict` arbitrário, declarando apenas o tipo das chaves e valores, sem usar um modelo Pydantic.

./mc cp /tmp/data/defpartsize minio1/test-bucket/defpartsize --enc-c "minio1/test-bucket/defpartsize=${TEST_MINIO_ENC_KEY}" --insecure

# Below should fail as compression and SSEC used at the same time
# DISABLED: We must check the response header to see if compression was actually applied
#RESULT=$({ ./mc put /tmp/data/mpartobj.txt minio1/test-bucket/mpartobj.txt --enc-c "minio1/test-bucket/mpartobj.txt=${TEST_MINIO_ENC_KEY}" --insecure; } 2>&1)

		if resp.Update != nil {
			select {
			case <-ctx.Done():
			case updates <- *resp.Update:
			}
		}
		if resp.Final != nil {
			final = resp.Final
		}
		// We can't reuse the response since it is sent upstream.
		return nil
	})
	if err != nil {
		return cache, toStorageErr(err)
	}
	if final == nil {
		return cache, errors.New("no final cache")
	}
	return *final, nil
}

<img src="/img/deployment/https/https05.drawio.svg">

### HTTP‑ответ { #http-response }

Приложение обработает запрос и отправит **обычный (незашифрованный) HTTP‑ответ** прокси‑серверу TLS-терминации.

<img src="/img/deployment/https/https06.drawio.svg">

### HTTPS‑ответ { #https-response }

    private int capabilities;

    /**
     * Constructs a session setup AndX request.
     *
     * @param tc the CIFS context containing configuration and credentials
     * @param negotiated the negotiation response containing server capabilities
     * @param andx the next command in the AndX chain, or null
     * @param cred the authentication credentials to use for the session
     * @throws SmbException if an SMB protocol error occurs

    /**
     * Negotiate RDMA parameters
     *
     * @param request negotiation request parameters
     * @return negotiation response
     * @throws IOException if negotiation fails
     */
    public abstract RdmaNegotiateResponse negotiate(RdmaNegotiateRequest request) throws IOException;

    /**
     * Reset connection after recoverable error

http://localhost:8000/items/?q=foo&q=bar
```

recibirías los múltiples valores del *query parameter* `q` (`foo` y `bar`) en una `list` de Python dentro de tu *path operation function*, en el *parámetro de función* `q`.

Entonces, el response a esa URL sería:

```JSON
{
  "q": [
    "foo",
    "bar"
  ]
}
```

/// tip | Consejo

If synchronous replication is configured above, replication is attempted right away prior to returning the PUT object response. In the event that the replication target is down, the `X-Amz-Replication-Status` is marked as `FAILED` and resynced with target when the scanner runs again.

            DcerpcPipeHandle handle = createMockedDcerpcPipeHandle();

            byte[] buf = new byte[50];
            byte[] inB = new byte[100];

            // Setup fragment length in response buffer
            Encdec.enc_uint16le((short) 40, inB, 8);

            when(mockSmbPipeHandleInternal.isStale()).thenReturn(false);