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).
Answer: To send a % sign in a url, instead send %25. In your case, in order for php to see a percent sign, you must pass the character string %25B6011000995504101^SB to the server. Why: In URLs, the percent sign has special meaning. Is used to encode special characters. For example, & is the separator … 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
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
General Answer The general answer to your question is that it depends. And you get to decide by specifying what your “Content-Type” is in the HTTP headers. A value of “application/x-www-form-urlencoded” means that your POST body will need to be URL encoded just like a GET parameter string. A value of “multipart/form-data” means that you’ll … Read more
Another way of doing this is using Uri.EscapeUriString(stringToEscape).
java.net.URLEncoder.encode(String s, String encoding) can help too. It follows the HTML form encoding application/x-www-form-urlencoded. URLEncoder.encode(query, “UTF-8”); On the other hand, Percent-encoding (also known as URL encoding) encodes space with %20. Colon is a reserved character, so : will still remain a colon, after encoding.
I faced the encoding half of this problem the other day. Unhappy with the available options, and after taking a look at this C sample code, i decided to roll my own C++ url-encode function: #include <cctype> #include <iomanip> #include <sstream> #include <string> using namespace std; string url_encode(const string &value) { ostringstream escaped; escaped.fill(‘0’); escaped … Read more