Random HTTP Method Routing Fixture Generator

Description

Construct supplied path/method requests and retain case-sensitive route permission, unknown-path and malformed-token decisions.

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 supplied path/method requests and retain case-sensitive route permission, unknown-path and malformed-token decisions.

When to use this tool

Use this generator to create reproducible http method routing 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 routes, paths, methods, invalidControl, count 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 requests. Use the conventions below and keep answer-bearing fields separate when presenting an exercise.

Draw a path and method, optionally append an invalid space-containing suffix, and delegate method-token checking. Classify invalid method first, then unknown path, exact case-sensitive allowed method, or method-not-allowed.^[1]

Delegated operations used for this result: method validator. Their calculation or parsing conventions apply to the corresponding result fields.^[2]

Input field	Meaning and units	Accepted input
routes	Routes	Required. Array of Object; no unknown keys.; minimum items 1; maximum items 16.
routes[].path	Path	Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 128.
routes[].methods	Methods	Required. Array of Text; minimum UTF-16 length 1; maximum UTF-16 length 128.; minimum items 0; maximum items 16.
paths	Paths	Required. Array of Text; minimum UTF-16 length 1; maximum UTF-16 length 128.; minimum items 1; maximum items 16.
methods	Methods	Required. Array of Text; minimum UTF-16 length 1; maximum UTF-16 length 128.; minimum items 1; maximum items 16.
invalidControl	Invalid Control	Required. Boolean.
count	Requested count; the mechanics explain whether one draw expands into several returned records.	Required. Safe integer; minimum 1; maximum 32.
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
requests	Requests	Required. Array of Object; no unknown keys.; minimum items 1; maximum items 32.
requests[].path	Path	Required. Text; maximum UTF-16 length 65536.
requests[].method	Method	Required. Text; maximum UTF-16 length 65536.
requests[].validMethod	Valid Method	Required. Boolean.
requests[].decision	Decision	Required. Text; one of "allowed", "unknown-path", "method-not-allowed", "invalid-method".
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.

json

{
  "input": {
    "routes": [
      {
        "path": "/read",
        "methods": [
          "GET"
        ]
      }
    ],
    "paths": [
      "/read"
    ],
    "methods": [
      "GET",
      "POST"
    ],
    "invalidControl": false,
    "count": 1,
    "seed": 42
  },
  "output": {
    "requests": [
      {
        "path": "/read",
        "method": "GET",
        "validMethod": true,
        "decision": "allowed"
      }
    ],
    "randomness": {
      "seed": 42,
      "source": "seed"
    }
  }
}

Limitations and assumptions

Method names are tokens and case-sensitive. This is an exact-path fixture with no wildcard routing, implicit HEAD/OPTIONS behavior, authentication, server, or request dispatch.
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

Tool behavior and example: Random HTTP Method Routing Fixture Generator — tool.io
Calculation or validation: http/method-validator — tool.io

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.