Solution skill
Signed URL fails with 401/400 when the source URL is partially encoded
Complete solution
Shows how to fix signed URL fails with 401/400 when the source URL is partially encoded. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
Pass the raw unencoded URL and let the SDK encode it, or upgrade past 1.1.1, which unescapes the input before re-escaping so mixed encoding signs correctly. Fixed in 1.1.1, which unescapes URLs before re-escaping them, and verified against the reporter's own URL.
Steps
- Issue imgix/imgix-python#21 (closed, 11 comments): signing a web-proxy source URL that mixed encoded (%20) and unencoded (~) characters produced bad signatures, first a 401 then a 400. The maintainer found the space was a red herring; the tilde was being encoded wrong. Fixed in 1.1.1, which unescapes URLs before re-escaping them, and verified against the reporter's own URL.
- The Python SDK expects unencoded source URLs. If you hand it a partially encoded URL (some characters encoded, some not), the signature will not match and imgix returns 401 or 400. Pass the raw unencoded URL and let the SDK encode it, or upgrade past 1.1.1, which unescapes the input before re-escaping so mixed encoding signs correctly. The classic tell is a %20 that signs fine while a nearby ~ breaks the signature.
When to use
You are seeing this: Issue imgix/imgix-python#21 (closed, 11 comments): signing a web-proxy source URL that mixed encoded (%20) and unencoded (~) characters produced bad signatures, first a 401 then a 400. Use this skill when you run into "Signed URL fails with 401/400 when the source URL is partially encoded".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
Versions mentioned in the source: 1.1.1. If you are on something much newer or older, the details may have shifted.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Evidence
In gh:imgix/imgix-python#21 (imgix), the issue reported was: Issue imgix/imgix-python#21 (closed, 11 comments): signing a web-proxy source URL that mixed encoded (%20) and unencoded (~) characters produced bad signatures, first a 401 then a 400. The maintainer found the space was a red herring; the tilde was being encoded wrong. Fixed in 1.1.1, which unescapes URLs before re-escaping them, and verified against the reporter's own URL. The verified resolution from the thread: The Python SDK expects unencoded source URLs. If you hand it a partially encoded URL (some characters encoded, some not), the signature will not match and imgix returns 401 or 400. Pass the raw unencoded URL and let the SDK encode it, or upgrade past 1.1.1, which unescapes the input before re-escaping so mixed encoding signs correctly. The classic tell is a %20 that signs fine while a nearby ~ breaks the signature. Source: mount the host path https at container path //github.com/imgix/imgix-python/issues/21
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_xLPoNlIWyuZ5815GudSDcQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Signed URL fails with 401/400 when the source URL is partially encoded <span>— Vectle</span></a>