url-encoding

How could I check if string has already been encoded? For example, if I encode TEST== , I get TEST%3D%3D . If I again encode last string, I get TEST%253D%253D , I would have to know before doing that if it is already encoded... I have encoded parameters saved, and I need to search for them. I don't know for input parameters, what will they be - encoded or not, so I have to know if I have to encode or decode them before search. 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

This question already has an answer here: HTTP URL Address Encoding in Java 24 answers i need java code to encode URL to avoid special characters such as spaces and % and & ...etc 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 encoded as "%20". RFC 2396 explains (in section 2.4.2) that a complete URL is always in its encoded form: you take

I'm POSTing data to an external API (using PHP, if it's relevant). Should I URL-encode the POST variables that I pass? Or do I only need to URL-encode GET data? Thanks! UPDATE: This is my PHP, in case it is relevant: $fields = array( 'mediaupload'=>$file_field, 'username'=>urlencode($_POST["username"]), 'password'=>urlencode($_POST["password"]), 'latitude'=>urlencode($_POST["latitude"]), 'longitude'=>urlencode($_POST["longitude"]), 'datetime'=>urlencode($_POST["datetime"]), 'category'=>urlencode($_POST["category"]), 'metacategory'=>urlencode($_POST["metacategory"]), 'caption'=>($_POST[

This question already has an answer here: URL encoding the space character: + or %20? 4 answers In a URL, should I encode the spaces using %20 or + ? For example, in the following example, which one is correct? www.mydomain.com?type=xbox%20360 www.mydomain.com?type=xbox+360 Our company is leaning to the former, but using the Java method URLEncoder.encode(String, String) with "xbox 360" (and "UTF-8" ) returns the latter . So, what's the difference? 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

To send username and password with a URL, we use this scheme: http://username:password@www.my_site.com But my username is my_email@gmail.com . The problem is the @ . How can I solve it? You need to URL encode the @ as %40. Use %40 in your username instead of the @ symbol for the url encoding. It should pass it properly then. Just do: http://my_email%40gmail.com:password@www.my_site.com I am quite surprised that problem was with username @ and not the password -usually this is where I get reserved characters in url authority or path parts. To solve general case of special characters: Just open