You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Normalize @scheme to lowercase per RFC 9421 §2.2.4 #45
The component value is the scheme as a lowercase string as defined in [HTTP], Section 4.2. While the scheme itself is case insensitive, it MUST be normalized to lowercase for inclusion in the signature base.
scScheme currently returns url.Scheme unchanged. Callers that set the scheme via MessageConfig.WithScheme (or otherwise supply a non-lowercase scheme) can therefore emit a non-compliant @scheme component.
parseRequest already sets "http" / "https" in lowercase when deriving from req.TLS, so the common path is fine; the gap is non-normalized scheme values from WithScheme / message construction.
Activity
yaronf commentedon Nov 14, 2026
Noted while reviewing #44 (@authority normalization). Tracking separately so that PR can stay focused.