apply {
      encodings[0x0] = encoding // Null character
      encodings[0x1] = encoding // Start of Header
      encodings[0x2] = encoding // Start of Text
      encodings[0x3] = encoding // End of Text
      encodings[0x4] = encoding // End of Transmission
      encodings[0x5] = encoding // Enquiry
      encodings[0x6] = encoding // Acknowledgment
      encodings[0x7] = encoding // Bell

* Decompressing gzip-compressed request bodies.
* Automatically logging all request bodies.

## Handling custom request body encodings { #handling-custom-request-body-encodings }

Let's see how to make use of a custom `Request` subclass to decompress gzip requests.

And an `APIRoute` subclass to use that custom request class.

/**
 * Servlet filter for handling character encoding conversion and URL redirection.
 * This filter processes requests with specific encoding requirements and converts
 * character encodings according to configured mapping rules.
 *
 * <p>The filter intercepts requests matching configured path patterns and
 * redirects them with proper character encoding applied to parameters.</p>
 */

But when the form includes files, it is encoded as `multipart/form-data`. You'll read about handling files in the next chapter.

If you want to read more about these encodings and form fields, head to the [<abbr title="Mozilla Developer Network">MDN</abbr> web docs for `POST`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods/POST).

///

/// warning

        return url;
    }

    /**
     * Extracts and processes the site path from a URL with proper encoding handling.
     * Removes protocol, query parameters, and applies URL decoding based on encoding settings.
     *
     * @param u the URL string to process
     * @param encoding the character encoding to use for URL decoding
     * @return the processed site path, abbreviated if necessary
     */

 * 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)

   * attribute values and in most elements' text contents, provided that the HTML
   * document's character encoding can encode any non-ASCII code points in the input (as UTF-8 and
   * other Unicode encodings can).
   *
   * <p><b>Note:</b> This escaper only performs minimal escaping to make content structurally

사용 사례에는 다음이 포함됩니다:

* JSON이 아닌 요청 바디를 JSON으로 변환하기(예: [`msgpack`](https://msgpack.org/index.html)).
* gzip으로 압축된 요청 바디 압축 해제하기.
* 모든 요청 바디를 자동으로 로깅하기.

## 커스텀 요청 바디 인코딩 처리하기 { #handling-custom-request-body-encodings }

커스텀 `Request` 서브클래스를 사용해 gzip 요청의 압축을 해제하는 방법을 살펴보겠습니다.

그리고 그 커스텀 요청 클래스를 사용하기 위한 `APIRoute` 서브클래스도 함께 보겠습니다.

### 커스텀 `GzipRequest` 클래스 만들기 { #create-a-custom-gziprequest-class }

/// tip | 팁

    }

    @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);

			// 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) {