The complicated way to achieve my goal was indeed to write my own javax.servlet.Filter and to embed it into the filter chain. This solution complies with the Apache Tomcat suggestion provided in Tomcat Wiki – Character Encoding Issues. Update (2010-07-31): The first version of this filter interpreted the query string itself, which was a bad … Read more
I filed a bug report with Apple about this, and heard back — with a very helpful response, no less! Turns out (much to my surprise) that it’s possible to successfully create Swift strings that contain invalid Unicode in the form of unpaired UTF-16 surrogate chars. Such a string can cause UTF-8 encoding to fail. … Read more
This will Work For You http://twitter.com/share?text=text goes here&url=http://url goes here&hashtags=hashtag1,hashtag2,hashtag3 Here is a Live Example About it http://twitter.com/share?text=Im Sharing on Twitter&url=https://stackoverflow.com/users/2943186/youssef-subehi&hashtags=stackoverflow,example,youssefusf
Decode, compare to original. If it does differ, original is encoded. If it doesn’t differ, original isn’t encoded. But still it says nothing about whether the newly decoded version isn’t still encoded. A good task for recursion. I hope one can’t write a quine in urlencode, or this algorithm would get stuck. Exception: When a … Read more
Simply calling ToString() on the NameValueCollection will return the name value pairs in a name1=value1&name2=value2 querystring ready format. Note that NameValueCollection types don’t actually support this and it’s misleading to suggest this, but the behavior works here due to the internal type that’s actually returned, as explained below. Thanks to @mjwills for pointing out that … Read more
The weird characters in the values passed in the URL should be escaped, using urlencode(). For example, the following portion of code : echo urlencode(‘dsf13f3343f23/23=’); would give you : dsf13f3343f23%2F23%3D Which works fine, as an URL parameter. And if you want to build aquery string with several parameters, take a look at the http_build_query() function. … Read more
A bit of explaining as to what that %2520 is : The common space character is encoded as %20 as you noted yourself. The % character is encoded as %25. The way you get %2520 is when your url already has a %20 in it, and gets urlencoded again, which transforms the %20 to %2520. … Read more
URL construction is tricky because different parts of the URL have different rules for what characters are allowed: for example, the plus sign is reserved in the query component of a URL because it represents a space, but in the path component of the URL, a plus sign has no special meaning and spaces are … Read more
Form data (for GET or POST) is usually encoded as application/x-www-form-urlencoded: this specifies + for spaces. URLs are encoded as RFC 1738 which specifies %20. In theory I think you should have %20 before the ? and + after: example.com/foo%20bar?foo+bar
You need to URL encode the @ as %40.