O local correto é:

* Na chave `content`, que tem como valor um outro objeto JSON (`dict`) que contém:
    * Uma chave com o media type, como por exemplo `application/json`, que contém como valor um outro objeto JSON, contendo::
        * Uma chave `schema`, que contém como valor o JSON Schema do modelo, sendo este o local correto.

labels.user_employeeType=Tipo de empleado
labels.employeeType=Tipo de empleado
labels.user_facsimileTelephoneNumber=Número de fax
labels.facsimileTelephoneNumber=Número de fax
labels.user_postOfficeBox=Apartado de correos
labels.postOfficeBox=Apartado de correos
labels.user_initials=Iniciales
labels.initials=Iniciales
labels.user_carLicense=Licencia de conducir
labels.carLicense=Licencia de conducir
labels.user_mobile=Teléfono móvil

class SmbPipeResourceTest {

    /**
     * Test if the PIPE_TYPE_RDONLY constant has the correct value.
     */
    @Test
    void testPipeTypeRdonly() {
        assertEquals(SmbConstants.O_RDONLY, SmbPipeResource.PIPE_TYPE_RDONLY, "PIPE_TYPE_RDONLY should match SmbConstants.O_RDONLY");
    }

    /**
     * Test if the PIPE_TYPE_WRONLY constant has the correct value.
     */
    @Test
    void testPipeTypeWronly() {

Luego, el navegador verificaría que el response sea válido y encriptado con la clave criptográfica correcta, etc. Entonces **desencriptaría el response** y lo procesaría.

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

El cliente (navegador) sabrá que el response proviene del servidor correcto porque está utilizando la criptografía que acordaron usando el **certificado HTTPS** anteriormente.

Mais peut‑être que votre application est hébergée à `https://mysuperapp.com`, et la redirection devrait être vers `https://mysuperapp.com/items/`.

En définissant `--proxy-headers`, FastAPI pourra désormais rediriger vers l'emplacement correct. 😎

```
https://mysuperapp.com/items/
```

/// tip | Astuce

Si vous voulez en savoir plus sur HTTPS, consultez le guide [À propos de HTTPS](../deployment/https.md).

///

        assertEquals(SmbComTransaction.TRANSACTION_BUF_SIZE, buffer2.length, "Reused buffer should have correct size");

        // Note: We don't check if content is cleared as that's not a security requirement
        // The important part is that the buffer is valid and has correct size
    }

    /**
     * Test getBuffers method for transaction buffers.
     */
    @Test

        assertThrows(CIFSException.class, () -> smbTreeHandle.close(), "close() should throw CIFSException");
    }

    /**
     * Test for isConnected() method.
     * Verifies that the method returns the correct connected status.
     */
    @Test
    void testIsConnected() {
        when(smbTreeHandle.isConnected()).thenReturn(true);
        assertTrue(smbTreeHandle.isConnected(), "isConnected() should return true");

			},
		},
		5: {
			desc:       "Correct sha256, nested",
			src:        mustReader(t, bytes.NewReader([]byte("abcd")), 4, "", "", 4),
			size:       4,
			actualSize: 4,
			sha256hex:  "88d4266fd4e6338d13b845fcf289579d209c897823b9217da3e161936f031589",
		},
		{
			desc:       "Correct sha256, nested, truncated",

        assertEquals(2, entries.length, "The number of entries should be correct.");

        // The getEntries method returns FileEntry objects. We can check their names.
        assertEquals("\\domain\share1", entries[0].getName(), "The name of the first share should be correct.");
        assertEquals("\\domain\share2", entries[1].getName(), "The name of the second share should be correct.");
    }

    /**

    class SamrCloseHandleTests {

        @Test
        @DisplayName("Should construct with correct opnum")
        void testConstructorAndOpnum() {
            // When: Creating close handle message
            samr.SamrCloseHandle message = new samr.SamrCloseHandle(mockPolicyHandle);

            // Then: Should have correct opnum and handle
            assertEquals(0x01, message.getOpnum());