Accept only explicitly supported document URL schemes
A customer enters a non-HTTP URI that the generic import library attempts to interpret as a local resource.
- Focused work estimate
- 1h 15m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Input validation · URL parsing
Estimated field mix
- Security70%
- API design30%
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 knowledge service imports documents from customer-entered URLs. The importer follows redirects and trusts response metadata too broadly.
Setup prerequisites
- Build a local fetch adapter and controlled HTTP test servers.
- Use synthetic documents and deny network access outside the test allowlist.
Preceding work
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Allow HTTPS under an explicit destination policy.
- Reject embedded credentials and unsupported schemes.
- Normalize once and retain a safe display URL.
Implementation constraints
- Use a standard URL parser; do not build one with string prefixes.
Verification to include
- Accept an approved synthetic HTTPS URL.
- Reject file, data and credential-bearing URLs before network calls.
Deliverables
- URL input policy and parser tests
Rollout and recovery
Enforce validation before import dispatch; quarantine existing unsupported requests.
Value of the work
For the engineer: Practice defensive URL handling and bounded untrusted-input processing.
For the team: Review whether integrations can import content without expanding infrastructure access.
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.