Description
Construct bounded relative or absolute synthetic redirect targets, resolving URLs and detecting an explicit loop or terminal response.
A protocol fixture is local test data representing headers, messages, identifiers, or request decisions. Serialization and parsing can be checked without contacting a server, while authentication, delivery, and actual client behavior require separate tests.
Construct bounded relative or absolute synthetic redirect targets, resolving URLs and detecting an explicit loop or terminal response.
When to use this tool
Use this generator to create reproducible http redirect chain fixture cases from the supplied model or bank. Inspect the returned evidence before using cases in a test or exercise.
How to use the tool and how it works
- Supply baseUrl, hops, statuses, styles, loop in the field shapes below. Set seed when you need an explicit replay.
- Run the tool and correct any input error. For generated controls, distinguish a successful fixture containing an invalid case from failure to generate the fixture.
- Read steps, finalUrl, stop, terminalStatus. Use the conventions below and keep answer-bearing fields separate when presenting an exercise.
Create a chain from the supplied origin's /s0 path, drawing redirect statuses and absolute or root-relative Location spellings. Resolve each hop and optionally point the last hop back to /s0, stopping when a previously seen URL recurs.1
Delegated operations used for this result: url; status category. Their calculation or parsing conventions apply to the corresponding result fields.2, 3
| Input field | Meaning and units | Accepted input |
|---|---|---|
| baseUrl | Base Url | Required. Text; maximum UTF-16 length 65536. |
| hops | Hops | Required. Safe integer; minimum 1; maximum 16. |
| statuses | Statuses | Required. Array of Safe integer; one of 301, 302, 303, 307, 308.; minimum items 1; maximum items 5. |
| styles | Styles | Required. Array of Text; one of "relative", "absolute".; minimum items 1; maximum items 2. |
| loop | Loop | Required. Boolean. |
| seed | Optional numeric seed; takes precedence over context randomness. Without either, use the fixed tool.io default seed. | Optional. Safe integer. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| steps | Steps | Required. Array of Object; no unknown keys.; minimum items 1; maximum items 16. |
| steps[].url | Url | Required. Text; maximum UTF-16 length 65536. |
| steps[].status | Named outcome; inspect null and error fields before interpreting associated values. | Required. Safe integer; minimum 301; maximum 308. |
| steps[].category | Category | Required. Text; maximum UTF-16 length 65536. |
| steps[].location | Location | Required. Text; maximum UTF-16 length 65536. |
| steps[].resolved | Resolved | Required. Text; maximum UTF-16 length 65536. |
| steps[].host | Host | Required. Text; maximum UTF-16 length 65536. |
| finalUrl | Final Url | Required. Text; maximum UTF-16 length 65536. |
| stop | Stop | Required. Text; one of "loop", "terminal". |
| terminalStatus | Terminal Status | Required. Safe integer; exactly 200. or Null. |
| randomness | Replay metadata: source is seed or context; seed is the normalized 32-bit seed or null for a context source. | Required. Object; no unknown keys. |
| randomness.seed | Optional numeric replay seed; normalization and precedence are explained below. | Required. Safe integer. or Null. |
| randomness.source | Source | Required. Text; one of "context", "seed". |
An explicit safe-integer seed takes precedence over injected context randomness and is normalized to an unsigned 32-bit integer. With no seed and no context source, replay uses the fixed tool.io default seed. A context source must return finite values from zero inclusive to one exclusive; its advancing state must be retained separately. randomness records the source and normalized seed, or null for context. These generators are not cryptographic random sources.
{
"input": {
"baseUrl": "https://example.com/start",
"hops": 2,
"statuses": [
302
],
"styles": [
"relative"
],
"loop": false,
"seed": 42
},
"output": {
"steps": [
{
"url": "https://example.com/s0",
"status": 302,
"category": "Redirection",
"location": "/s1",
"resolved": "https://example.com/s1",
"host": "example.com"
},
{
"url": "https://example.com/s1",
"status": 302,
"category": "Redirection",
"location": "/s2",
"resolved": "https://example.com/s2",
"host": "example.com"
}
],
"finalUrl": "https://example.com/s2",
"stop": "terminal",
"terminalStatus": 200,
"randomness": {
"seed": 42,
"source": "seed"
}
}
}Limitations and assumptions
- The base path is not retained. terminalStatus 200 is synthetic and null for a loop; no HTTP response, method rewriting, credential forwarding, or network request is executed.
- A replay requires the same complete input and implementation. Randomized construction does not guarantee uniform coverage of every feasible output; finite samples can repeat unless a distinct-selection rule is explicitly stated.
- The field tables state structural bounds; cross-field constraints and bounded search or output budgets also apply. Unknown keys are rejected where the object contract disallows them. Input errors are distinct from null fields and deliberate invalid controls in a successful output.
Alternative or Complementary methods
For a supplied example, inspect the returned construction or delegated check directly. To evaluate a consumer, also test cases chosen for its own boundaries; a generated finite corpus does not establish exhaustive coverage.
References
Similar or alternative tools
- Random HTTP Basic Auth Parser Corpus Generator
Construct synthetic ASCII Basic credential bytes and malformed controls, preserving delegated split and error outcomes without real credentials.
- Random HTTP Bearer Shape Corpus Generator
Construct fake Bearer header casing and whitespace variants with malformed-token controls and delegated extraction answers.