Description
Construct synthetic credential URLs, extract encoded members and strip complete userinfo from normalized HTTP(S) URLs.
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 synthetic credential URLs, extract encoded members and strip complete userinfo from normalized HTTP(S) URLs.
When to use this tool
Use this generator to create reproducible url credential redaction 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
- Supply baseUrl, usernames, passwords, 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 cases. Use the conventions below and keep answer-bearing fields separate when presenting an exercise.
Draw supplied usernames/passwords, URI-encode the userinfo members and construct a synthetic credential URL on the normalized base. Delegate credential extraction and return a redacted URL with the complete userinfo removed.1
Delegated operations used for this result: url username; url password. Their calculation or parsing conventions apply to the corresponding result fields.2, 3
| Input field | Meaning and units | Accepted input |
|---|---|---|
| baseUrl | Base Url | Required. Text; maximum UTF-16 length 65536. |
| usernames | Usernames | Required. Array of Text; maximum UTF-16 length 65536.; minimum items 1; maximum items 16. |
| passwords | Passwords | Required. Array of Text; maximum UTF-16 length 65536.; minimum items 1; maximum items 16. |
| 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 |
|---|---|---|
| cases | Cases | Required. Array of Object; no unknown keys.; minimum items 1; maximum items 32. |
| cases[].url | Url | Required. Text; maximum UTF-16 length 65536. |
| cases[].username | Username | Required. Text; maximum UTF-16 length 65536. |
| cases[].password | Password | Required. Text; maximum UTF-16 length 65536. |
| cases[].redacted | Redacted | Required. Text; maximum UTF-16 length 65536. |
| 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.
{
"input": {
"baseUrl": "https://example.com/account",
"usernames": [
"reader",
"guest"
],
"passwords": [
"p:a"
],
"count": 1,
"seed": 42
},
"output": {
"cases": [
{
"url": "https://guest:p%3Aa@example.com/account",
"username": "guest",
"password": "p%3Aa",
"redacted": "https://example.com/account"
}
],
"randomness": {
"seed": 42,
"source": "seed"
}
}
}Limitations and assumptions
- Use synthetic credentials. Extracted username/password spellings may remain percent-encoded; redaction here removes userinfo, not every possible secret in a path, query, fragment or external log.
- 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
Similar or alternative tools
- Random URL Fragment Routing Fixture Generator
Construct supplied query and fragment combinations with encoded, empty and absent fragment controls and delegated hash expectations.
- Random URL Origin Comparison Quiz Generator
Construct HTTP(S) URL mutations and compare normalized scheme, host and port origins without live requests.