Skip to content

Main content

Csp Wildcard Port Source Token Tool

Compute csp wildcard port source token from explicit bounded inputs.

Loading tool…

Description

Parse source as a host-like token followed by colon and either star or one through five digits.

Web protocol data has several layers: a complete message or URL, individual fields or components, and the literal tokens within them. Delimiter presence, spelling, comparison rules, and parser normalization can affect results. A check of one component needs its stated scope before it can be used in a larger parser or policy decision.

Parse source as a host-like token followed by colon and either star or one through five digits.

When to use this tool

Use Csp Wildcard Port Source Token when you need one stated URL, header, or protocol-component check in a diagnostic or parser workflow. Supply the input level specified below.

How to use the tool and how it works

  1. Enter source. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read host, wildcardPort. Inspect wildcardPort before interpreting the associated values.

Parse source as a host-like token followed by colon and either star or one through five digits. Validate numeric ports from one through 65535, then return host and wildcardPort.1

Input fieldMeaning and unitsAccepted input
sourceSourceRequired. Text; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
hostHostRequired. Text; maximum UTF-16 length 8192.
wildcardPortWildcard PortRequired. Boolean.
json
{
  "input": {
    "source": "example.com:*"
  },
  "output": {
    "host": "example.com",
    "wildcardPort": true
  }
}

Limitations and assumptions

  • This lexical source has no scheme, path, or IPv6 support and does not validate DNS label rules or wildcard placement. It is not a full CSP source-expression validator or browser matching decision.
  • The field tables state structural bounds; the mechanics also specify cross-field constraints. Malformed inputs and unsupported domains cause errors. A successful false flag, empty branch value, or zero placeholder has the meaning stated above and is distinct from an input error.

Alternative or Complementary methods

Use a complete URL or header parser when the task involves an entire field or message. Test actual browser, server, or cache behavior separately when a security or protocol decision depends on more than this component.

References

  1. Calculation and input contract: web/csp-wildcard-port-source-token — tool.io

Similar or alternative tools