// (where timestamps are stored as the number of seconds since the Unix epoch).
//
// The table's lower portion shows specialized features of each format,
// such as supported string encodings, support for sub-second timestamps,
// or support for sparse files.
//
// The Writer currently provides no support for sparse files.
type Format int

// Constants to identify various tar formats.
const (

            assertArrayEquals(ASCII_STRING.getBytes(StandardCharsets.US_ASCII), result, "Should produce same bytes as ASCII encoding");
        }
    }

    @Nested
    @DisplayName("OEM Encoding Tests")
    class OEMEncodingTests {

        @Test
        @DisplayName("getOEMBytes should use configuration encoding")
        void testGetOEMBytes() {

 * and {@link Key} objects, with configurable algorithms and character encodings.
 * </p>
 * <p>
 * <strong>Key Features:</strong>
 * </p>
 * <ul>
 * <li>Thread-safe cipher pooling using {@link ConcurrentLinkedQueue}</li>
 * <li>Configurable encryption algorithms (default: Blowfish)</li>
 * <li>Proper charset handling for key generation (UTF-8 by default)</li>
 * <li>Base64 encoding for text operations</li>
 * </ul>
 * <p>

    public void testEncodingMethod() {
        CurlRequest request = new CurlRequest(Method.GET, "https://example.com");
        String encoding = "ISO-8859-1";

        CurlRequest result = request.encoding(encoding);

        assertSame(request, result); // Fluent API
        assertEquals(encoding, request.encoding());
    }

    @Test
    public void testEncodingAfterParamThrowsException() {

	// RestoreOngoing indicates if a restore is in progress
	RestoreOngoing bool

	// A standard MIME type describing the format of the object.
	ContentType string

	// Specifies what content encodings have been applied to the object and thus
	// what decoding mechanisms must be applied to obtain the object referenced
	// by the Content-Type header field.
	ContentEncoding string

	// Hex constant 0x20004000000
	MOVD $2199090364416, R5         // 60058001
	// Hex constant 0xFFFFFE0004000000
	MOVD $-2198956146688, R5        // 38a08001
	// TODO: On GOPPC64={power8,power9}, this is preprocessed into MOVD $-1, R5; RLDC R5, $33, $63, R5.
	//       This only captures the MOVD. Should the RLDC be appended to the encoding by the test?
	// Hex constant 0xFFFFFFFE00000001

 * return hex.decode("deadbeef"); // throws an IllegalArgumentException
 * }
 *
 * <p>It is guaranteed that {@code encoding.decode(encoding.encode(x))} is always equal to {@code
 * x}, but the reverse does not necessarily hold.
 *
 * <table>
 * <caption>Encodings</caption>
 * <tr>
 * <th>Encoding
 * <th>Alphabet
 * <th>{@code char:byte} ratio
 * <th>Default padding
 * <th>Comments
 * <tr>
 * <td>{@link #base16()}

- Розпакування тіл запитів, стиснених gzip.
- Автоматичне логування всіх тіл запитів.

## Обробка користувацьких кодувань тіла запиту { #handling-custom-request-body-encodings }

Розгляньмо, як використати користувацький підклас `Request` для розпакування gzip-запитів.

А також підклас `APIRoute`, щоб застосувати цей користувацький клас запиту.

* gzip ile sıkıştırılmış request body'leri açmak (decompress).
* Tüm request body'lerini otomatik olarak loglamak.

## Özel request body encoding'lerini ele alma { #handling-custom-request-body-encodings }

Gzip request'lerini açmak için özel bir `Request` alt sınıfını nasıl kullanabileceğimize bakalım.

Ayrıca, o özel request sınıfını kullanmak için bir `APIRoute` alt sınıfı da oluşturacağız.

* Распаковка тел запросов, сжатых с помощью gzip.
* Автоматическое логирование всех тел запросов.

## Обработка пользовательского кодирования тела запроса { #handling-custom-request-body-encodings }

Посмотрим как использовать пользовательский подкласс `Request` для распаковки gzip-запросов.

И подкласс `APIRoute`, чтобы использовать этот пользовательский класс запроса.