Skip to content

Main content

Random HTTP Content Type Parameter Corpus Generator

Construct caller-supplied media types with escaped parameter quoting and duplicate-name controls, retaining delegated parse results.

Loading tool…

Description

Construct caller-supplied media types with escaped parameter quoting and duplicate-name controls, retaining delegated parse results.

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 caller-supplied media types with escaped parameter quoting and duplicate-name controls, retaining delegated parse results.

When to use this tool

Use this generator to create reproducible http content type parameter corpus 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

  1. Supply mediaTypes, parameters, duplicateControl, count in the field shapes below. Set seed when you need an explicit replay.
  2. 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.
  3. Read cases. Use the conventions below and keep answer-bearing fields separate when presenting an exercise.

Draw media types and parameter values, quote and escape values when token syntax requires it, and optionally duplicate the first parameter. Delegate Content-Type parsing and retain actual acceptance, normalized result, or parser issue.1

Delegated operations used for this result: content type parser. Their calculation or parsing conventions apply to the corresponding result fields.2

Input fieldMeaning and unitsAccepted input
mediaTypesMedia TypesRequired. Array of Text; maximum UTF-16 length 65536.; minimum items 1; maximum items 16.
parametersParametersRequired. Array of Object; no unknown keys.; minimum items 1; maximum items 8.
parameters[].nameNameRequired. Text; maximum UTF-16 length 65536.
parameters[].valuesValuesRequired. Array of Text; maximum UTF-16 length 65536.; minimum items 1; maximum items 16.
duplicateControlDuplicate ControlRequired. Boolean.
countRequested count; the mechanics explain whether one draw expands into several returned records.Required. Safe integer; minimum 1; maximum 32.
seedOptional numeric seed; takes precedence over context randomness. Without either, use the fixed tool.io default seed.Optional. Safe integer.
Output fieldInterpretationReturned shape
casesCasesRequired. Array of Object; no unknown keys.; minimum items 1; maximum items 32.
cases[].headerHeaderRequired. Text; maximum UTF-16 length 65536.
cases[].acceptedAcceptedRequired. Boolean.
cases[].mediaTypeMedia TypeRequired. Text; maximum UTF-16 length 65536.
cases[].parametersParametersRequired. Array of Object; no unknown keys.; minimum items 0; maximum items 9.
cases[].parameters[].nameNameRequired. Text; maximum UTF-16 length 65536.
cases[].parameters[].valueValueRequired. Text; maximum UTF-16 length 65536.
cases[].errorCodeError CodeRequired. Text; maximum UTF-16 length 65536.
randomnessReplay 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.seedOptional numeric replay seed; normalization and precedence are explained below.Required. Safe integer. or Null.
randomness.sourceSourceRequired. 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": {
    "mediaTypes": [
      "text/plain"
    ],
    "parameters": [
      {
        "name": "charset",
        "values": [
          "utf 8"
        ]
      }
    ],
    "duplicateControl": false,
    "count": 1,
    "seed": 42
  },
  "output": {
    "cases": [
      {
        "header": "text/plain; charset=\"utf 8\"",
        "accepted": true,
        "mediaType": "text/plain",
        "parameters": [
          {
            "name": "charset",
            "value": "utf 8"
          }
        ],
        "errorCode": ""
      }
    ],
    "randomness": {
      "seed": 42,
      "source": "seed"
    }
  }
}

Limitations and assumptions

  • Duplicate controls are interpreted by the linked parser rather than assumed accepted. This checks header syntax only, not body encoding, charset conversion, content sniffing, or a response's actual media format.
  • 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

  1. Tool behavior and example: Random HTTP Content Type Parameter Corpus Generator — tool.io

  2. Calculation or validation: http/content-type-parser — tool.io

Similar or alternative tools