Trace
Requirement → acceptance criteria → tasks → commits → pull requests → reviews, with each criterion's AI verdict and its verification on the latest build.
REQ-CLICK-01: Terminal output respects user configuration REQ-CLICK-02: Styled output degrades gracefully REQ-CLICK-03: Breaking changes are announced one minor release ahead REQ-HTTPX-01: TLS configuration has one obvious way REQ-HTTPX-02: URLs are encoded the way browsers encode them REQ-HTTPX-03: Secrets never appear in logs REQ-REQ-01: Anything that behaves like a file is accepted REQ-REQ-02: Public type hints describe what callers may pass REQ-REQ-03: Security-relevant code works under FIPS SUB-CLI-01: Command-line output library (click) meets the baseline SUB-HTTP-01: HTTP client libraries (requests, httpx) meet the baseline SYS-01: Third-party client libraries meet the platform dependency baseline
REQ-HTTPX-02 · v1 changed 2024-10-20
Percent-encoding follows the WHATWG URL standard.
3 acceptance criteria
Query parameters encode spaces as `+` (form encoding).
A `/` inside a query parameter value is percent-encoded as `%2F`.
The behaviour change is called out in the CHANGELOG under backwards-incompatible changes.
TASK-HTTPX-2011 done
TASK-HTTPX-2012 done