Description
Compare a CSP port selector with an explicit or default destination port; scheme, host and path matching are separate operations.
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.
Compare a CSP port selector with an explicit or default destination port; scheme, host and path matching are separate operations.
When to use this tool
Use CSP Wildcard Port Domain Flag 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
- Enter sourcePort, destinationPort, schemeDefaultPort, destinationPortExplicit. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read portMatches. Inspect portMatches before interpreting the associated values.
Require integer destinationPort and schemeDefaultPort from zero through 65535, and sourcePort empty, star, or decimal text no greater than 65535. Star matches every port; empty source matches only when destinationPortExplicit is false; numeric source compares with explicit destination or supplied default.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| sourcePort | Empty, star, or decimal source-port spelling under the simplified model. | Required. Text; maximum UTF-16 length 8192. |
| destinationPort | Destination Port | Required. Safe integer; minimum 0; maximum 65535. |
| schemeDefaultPort | Scheme Default Port | Required. Safe integer; minimum 0; maximum 65535. |
| destinationPortExplicit | Whether the destination is modeled with an explicit port. | Required. Boolean. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| portMatches | Port Matches | Required. Boolean. |
{
"input": {
"sourcePort": "*",
"destinationPort": 8443,
"schemeDefaultPort": 443,
"destinationPortExplicit": true
},
"output": {
"portMatches": true
}
}Limitations and assumptions
- The empty-source rule is this tool's simplified flag model, not complete CSP matching. Scheme upgrades, host checks, effective default equivalence, and browser policy enforcement require a separate evaluation.
- 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
Similar or alternative tools
- Csp Wildcard Port Source Token
Parse source as a host-like token followed by colon and either star or one through five digits.
- CSP Host Source Subdomain Wildcard Pair
Check only a lowercase ASCII host subdomain wildcard; scheme, port and path matching are outside this fragment.