For the URI query use urlencode/urldecode; for anything else use rawurlencode/rawurldecode. The difference between urlencode and rawurlencode is that urlencode encodes according to application/x-www-form-urlencoded (space is encoded with +) while rawurlencode encodes according to the plain Percent-Encoding (space is encoded with %20).
I think you’re stuck with what C# gives you, and getting errors suggests a poorly implemented UrlDecode function on the other end. With that said, you should just need to loop through the string and uppercase only the two characters following a % sign. That’ll keep your base64 data intact while massaging the encoded characters … Read more
System.Uri.EscapeUriString() can be problematic with certain characters, for me it was a number / pound ‘#’ sign in the string. If that is an issue for you, try: System.Uri.EscapeDataString() //Works excellent with individual values Here is a SO question answer that explains the difference: What’s the difference between EscapeUriString and EscapeDataString? and recommends to use … Read more
Jersey’s UriBuilder encodes URI components using application/x-www-form-urlencoded and RFC 3986 as needed. According to the Javadoc Builder methods perform contextual encoding of characters not permitted in the corresponding URI component following the rules of the application/x-www-form-urlencoded media type for query parameters and RFC 3986 for all other components. Note that only characters not permitted in … Read more
Without seeing your code, it’s hard to answer other than a stab in the dark. I would guess that the string you’re passing to encodeURIComponent(), which is the correct method to use, is coming from the result of accessing the innerHTML property. The solution is to get the innerText/textContent property value instead: var str, el … Read more
Check out http://www.asciitable.com/ Look at the Hx, (Hex) column; 2C maps to , Any unusual encoding can be checked this way +—-+—–+—-+—–+—-+—–+—-+—–+ | Hx | Chr | Hx | Chr | Hx | Chr | Hx | Chr | +—-+—–+—-+—–+—-+—–+—-+—–+ | 00 | NUL | 20 | SPC | 40 | @ | 60 | … Read more
Background It’s a bit more subtle than one might think at first sight. For any URL, which is a specific form of the URI standard, certain characters are special. Among the special characters are `:` (scheme separator) and `/` (path or hierarchy separator), here’s the full list of reserved symbols from [RFC-2396][1]: reserved = “;” … Read more
The answer to the question, “what am I doing wrong,” is that the shell sees the ampersand (&) and thinks that’s the end of the command (and puts it into the background). You need to quote it, which is why the answers that quoted the string work. You could just as easily run this: curl … Read more
The + character has a special meaning in a URL => it means whitespace – . If you want to use the literal + sign, you need to URL encode it to %2b: body=Hi+there%2bHello+there Here’s an example of how you could properly generate URLs in .NET: var uriBuilder = new UriBuilder(“https://mail.google.com/mail”); var values = HttpUtility.ParseQueryString(string.Empty); … Read more
I didn’t find the existing answers satisfactory so I decided to dig a little deeper to settle this issue. Surprisingly, the answer is very simple: There is (almost) no valid reason to ever use Uri.EscapeUriString. If you need to percent-encode a string, always use Uri.EscapeDataString.* * See the last paragraph for a valid use case. … Read more