roleQueryHelper.setEncryptedParameterValue(false);
        assertFalse(roleQueryHelper.encryptedParameterValue);

        roleQueryHelper.setHeaderKey("header");
        assertEquals("header", roleQueryHelper.headerKey);

        roleQueryHelper.setEncryptedHeaderValue(false);
        assertFalse(roleQueryHelper.encryptedHeaderValue);

        roleQueryHelper.setCookieKey("cookie");

        }

        return this.size;
    }

    private static String readString(final byte[] buffer, int bufferIndex, final int len) {
        // this is not absolutely correct, but we assume that the header is aligned
        if (bufferIndex % 2 != 0) {
            bufferIndex++;
        }
        return Strings.fromUNIBytes(buffer, bufferIndex, Strings.findUNITermination(buffer, bufferIndex, len));
    }

# When we use Patchelf versions <0.12, those shared libraries end up with a
# corrupted PT_NOTE program header. This was fixed in v0.12, see https://github.com/NixOS/patchelf/commit/43a33482b501b0f5ee9da312aabfca3806570cc9.

///

## Agrega headers personalizados

Existen algunas situaciones en las que es útil poder agregar headers personalizados al error HTTP. Por ejemplo, para algunos tipos de seguridad.

Probablemente no necesitarás usarlos directamente en tu código.

Pero en caso de que los necesites para un escenario avanzado, puedes agregar headers personalizados:

    // Helper to create a fresh request under test
    private Smb2LogoffRequest newRequest() {
        return new Smb2LogoffRequest(configuration);
    }

    @Test
    @DisplayName("size() returns 8-byte aligned value (header + 4)")
    void size_returnsAlignedValue() {
        // Arrange
        Smb2LogoffRequest req = newRequest();
        int base = Smb2Constants.SMB2_HEADER_LENGTH + 4; // structure size

        // Mock getHeaderFields to return our headers
        Map<String, List<String>> allHeaders = headers != null ? new HashMap<>(headers) : new HashMap<>();
        allHeaders.put(null, Collections.singletonList(statusLine)); // Status line
        when(conn.getHeaderFields()).thenReturn(allHeaders);

        // Mock individual header access by both string key and index
        if (headers != null) {
            // Mock by header name

  * As part of preparation in 1.2 for adding support for protocol buffers (and the
direct YAML support in the API available today), the Content-Type and Accept
headers are now properly handled as per the HTTP spec.  As a consequence, if
you had a client that was sending an invalid Content-Type or Accept header to
the API, in 1.2 you will either receive a 415 or 406 error.
The only client
this is known to affect is curl when you use -d with JSON but don't set a

        int bufferIndex = 100; // Start at non-zero index

        // Set structure size to 9 (valid)
        SMBUtil.writeInt2(9, buffer, bufferIndex);
        // Set buffer offset (relative to header start)
        SMBUtil.writeInt2(50, buffer, bufferIndex + 2);
        // Set buffer length
        SMBUtil.writeInt4(8, buffer, bufferIndex + 4);

        // Mock getHeaderStart
        response = spy(response);

 * See the License for the specific language governing permissions and
 * limitations under the License.
 */
package okhttp3.internal.http2.hpackjson

/**
 * Representation of one story, a set of request headers to encode or decode. This class is used
 * reflectively with Moshi to parse stories from files.
 */
data class Story(
  val description: String? = null,
  val cases: List<Case>,
  val fileName: String? = null,
) {

        .build()

    client.newCall(request).execute().use { response ->
      if (!response.isSuccessful) throw IOException("Unexpected code $response")

      for ((name, value) in response.headers) {
        println("$name: $value")
      }

      println(response.body.string())
    }
  }
}

fun main() {
  SynchronousGet().run()