Skip to content

Main content
Bookmark this: tool.io/random/url-origin-comparison-quiz

Random URL Origin Comparison Quiz Generator

Construct HTTP(S) URL mutations and compare normalized scheme, host and port origins without live requests.

Loading tool…

Description

Construct HTTP(S) URL mutations and compare normalized scheme, host and port origins without live requests.

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 HTTP(S) URL mutations and compare normalized scheme, host and port origins without live requests.

When to use this tool

Use this generator to create reproducible url origin comparison quiz 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 baseUrl, mutations, 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 pairs. Use the conventions below and keep answer-bearing fields separate when presenting an exercise.

Draw a path, scheme, host or port mutation of the supplied HTTP(S) base URL. Delegate normalized origin extraction for both URLs and compare the resulting scheme/host/port origin strings.1

Delegated operations used for this result: url origin. Their calculation or parsing conventions apply to the corresponding result fields.2

Input fieldMeaning and unitsAccepted input
baseUrlBase UrlRequired. Text; maximum UTF-16 length 65536.
mutationsMutationsRequired. Array of Text; one of "path", "scheme", "host", "port".; minimum items 1; maximum items 4.
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
pairsPairsRequired. Array of Object; no unknown keys.; minimum items 1; maximum items 32.
pairs[].leftLeftRequired. Text; maximum UTF-16 length 65536.
pairs[].rightRightRequired. Text; maximum UTF-16 length 65536.
pairs[].mutationMutationRequired. Text; maximum UTF-16 length 65536.
pairs[].leftOriginLeft OriginRequired. Text; maximum UTF-16 length 65536.
pairs[].rightOriginRight OriginRequired. Text; maximum UTF-16 length 65536.
pairs[].sameOriginSame OriginRequired. Boolean.
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": {
    "baseUrl": "https://EXAMPLE.com:443/a",
    "mutations": [
      "scheme",
      "path"
    ],
    "count": 2,
    "seed": 42
  },
  "output": {
    "pairs": [
      {
        "left": "https://example.com/a",
        "right": "https://example.com/changed/1",
        "mutation": "path",
        "leftOrigin": "https://example.com",
        "rightOrigin": "https://example.com",
        "sameOrigin": true
      },
      {
        "left": "https://example.com/a",
        "right": "http://example.com/a",
        "mutation": "scheme",
        "leftOrigin": "https://example.com",
        "rightOrigin": "http://example.com",
        "sameOrigin": false
      }
    ],
    "randomness": {
      "seed": 42,
      "source": "seed"
    }
  }
}

Limitations and assumptions

  • Path changes can preserve origin; default-port normalization is part of URL parsing. sameOrigin is not a CORS, authorization, cookie or network-access decision.
  • 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 URL Origin Comparison Quiz Generator — tool.io

  2. Calculation or validation: web/url-origin — tool.io

Similar or alternative tools

Support Tool.io