Normalize import URLs without changing their authority
User-info syntax and encoded separators confuse destination checks.
- Focused work estimate
- 3h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- URL security
Estimated field mix
- Security80%
- Networking20%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional content-import service accepts document URLs. The team needs explicit destination approval, redirect handling, and response limits before enabling imports.
Setup prerequisites
- Create a local HTTP destination simulator and DNS double with authorized address cases; contact no real external hosts.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Parse URLs with a single canonical parser.
- Reject credentials, ambiguous encodings, and unsupported schemes.
- Compare normalized authority against policy.
Implementation constraints
- Do not perform a request during validation.
Verification to include
- Normalize an approved URL deterministically.
- Reject user-info and authority-confusion fixtures.
Deliverables
- URL validation boundary.
Rollout and recovery
Run validation before queueing any fetch.
Value of the work
For the engineer: Practice URL interpretation, network policy enforcement, and resource controls.
For the team: Provide a reusable fetch boundary that makes destination authority and failure behavior inspectable.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.