// mime package in MinIO, which correctly encodes strings with fixed B/Q encodings,
			// avoiding S3’s heuristic-driven issues.
			//
			// For MinIO developers, decode S3 metadata with mime.WordDecoder, validate outputs,
			// report encoding bugs to AWS, and use ASCII-only metadata to ensure reliable S3 API
			// compatibility.
			if needsMimeEncoding(v) {

 * the tests create a mock {@link Configuration} and instantiate SmbComQueryInformation
 * directly.  Since the byte‑encoding logic is located in the superclass, the
 * tests verify that the byte buffer created by {@link
 * SmbComQueryInformation#writeBytesWireFormat(byte[], int)} is correctly built
 * for both Unicode and OEM encodings.
 */
@ExtendWith(MockitoExtension.class)
@MockitoSettings(strictness = Strictness.LENIENT)

    }

    @Test
    @DisplayName("should handle different charset encodings correctly")
    void shouldHandleDifferentCharsetEncodingsCorrectly() {
        Terminal mockTerminal = mock(Terminal.class);

        // Test with ISO-8859-1 (Latin-1) - should support some but not all Unicode chars
        when(mockTerminal.encoding()).thenReturn(StandardCharsets.ISO_8859_1);

// equivalent to that from a range loop over the input as a string, which
// means that erroneous UTF-8 encodings translate to U+FFFD = "\xef\xbf\xbd".
// Because of the Scan interface, this makes it impossible for the client to
// distinguish correctly encoded replacement runes from encoding errors.
func ScanRunes(data []byte, atEOF bool) (advance int, token []byte, err error) {
	if atEOF && len(data) == 0 {

        verify(mockNdrBuffer).enc_ndr_referent(shareInfo502.security_descriptor, 1);

        // Verify string encodings
        verify(mockDeferredBuffer, times(4)).enc_ndr_string(anyString());

        // Verify security descriptor encoding
        verify(mockDeferredBuffer).enc_ndr_long(2);
        verify(mockDeferredBuffer).advance(2);
        verify(mockDeferredBuffer).enc_ndr_small((byte) 1);

But when the form includes files, it is encoded as `multipart/form-data`. If you use `File`, **FastAPI** will know it has to get the files from the correct part of the body.

If you want to read more about these encodings and form fields, head to the <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods/POST" class="external-link" target="_blank"><abbr title="Mozilla Developer Network">MDN</abbr> web docs for <code>POST</code></a>.

///

* Descomprimir cuerpos de requests comprimidos con gzip.
* Registrar automáticamente todos los request bodies.

## Manejo de codificaciones personalizadas de request body { #handling-custom-request-body-encodings }

Veamos cómo hacer uso de una subclase personalizada de `Request` para descomprimir requests gzip.

Y una subclase de `APIRoute` para usar esa clase de request personalizada.

* Descomprimir corpos de requisição comprimidos com gzip.
* Registrar automaticamente todos os corpos de requisição.

## Manipulando codificações de corpo de requisição personalizadas { #handling-custom-request-body-encodings }

Vamos ver como usar uma subclasse personalizada de `Request` para descomprimir requisições gzip.

E uma subclasse de `APIRoute` para usar essa classe de requisição personalizada.

            // Verify reserved section is zero
            assertEquals(0, SMBUtil.readInt4(buffer, 20));
        }

        @Test
        @DisplayName("Should handle multiple sequential encodings")
        void testMultipleSequentialEncodings() {
            // Given
            SrvCopychunk chunk1 = new SrvCopychunk(100, 200, 300);
            SrvCopychunk chunk2 = new SrvCopychunk(400, 500, 600);

     * has a charset other than utf-8 the behaviour differs by platform.
     *
     * On the JVM the encoding will be used instead of utf-8.
     *
     * On non JVM platforms, this method will fail for encodings other than utf-8.
     */
    @JvmStatic
    @JvmName("create")
    fun String.toResponseBody(contentType: MediaType? = null): ResponseBody {