Observe a bounded HTTP request

Prediction

Changing the method or adding fixed request content should change the normalized request description. A HEAD response should carry metadata without content.

Controlled observation

Choose a GET with Accept, a POST with a fixed text representation, or HEAD. The Worker reports only the method, UTF-8 content byte count, and a small allowlist of normalized field values.

Explanation

An HTTP message combines control data, fields, and optional content. This echo is intentionally incomplete: it demonstrates those parts without reflecting credentials, arbitrary fields, raw binary data, or visitor-selected content.

HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8
X-Lab-Scenario: anything

{"request":{"bodyBytes":0,"headers":{"accept":"application/json"},"method":"GET"},"scenario":"anything"}

'curl' '--include' '--request' 'GET' '--header' 'Accept: application/json' 'https://lab.httpclarity.com/v1/anything'

const response = await fetch("https://lab.httpclarity.com/v1/anything", {
  "method": "GET",
  "headers": {
    "Accept": "application/json"
  }
});
console.log(response.status, await response.text());

<?php
$options = ['http' => [
    'method' => 'GET',
    'ignore_errors' => true,
    'header' => 'Accept: application/json',
]];
$context = stream_context_create($options);
$body = file_get_contents('https://lab.httpclarity.com/v1/anything', false, $context);
var_dump($http_response_header, $body);