Replies: 1 comment 9 replies
-
Seeing: #200 (comment) "trurl only outputs valid URLs" - I believe then only Edit: nevermind, percent-encoded URLs are valid! curl/curl#7830 |
Beta Was this translation helpful? Give feedback.
9 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
For anyone finding needing this
Read #219 (reply in thread) 🙂
Original text:
Is it too out-of-scope to wish for encoding and decoding URL percent-encoding? A quick search shows there are dozens of code-golfed one liners in the wild, but nothing as simple as
echo $URL | trurl --%-decode
... (It's nice that % isn't a special character in bash...)A problematic example is trying to use curl on something like
curl https%3A%2F%2Fsecure.gravatar.com%2F
- curl will report a bad hostname. It'd be great if anyone could dotrurl --%-decode https%3A%2F%2Fsecure.gravatar.com%2F | curl
Beta Was this translation helpful? Give feedback.
All reactions