Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
http://www.w3schools.com/tags/ref_urlencode.asp
Since URLs often contain characters outside the ASCII set, the URL has
to be converted into a valid ASCII format.
But both space, /, % are part of the ASCII character set, so why encode them in the first place? What characters should be encoded?
As noted, spaces are not valid in URLs. Most browsers orlencode them automatically. However…
The page you linked to has an example using the word “Günter” in the “Try me” section. If the word “Günter” were sent as a querystring parameter, it wouldn’t work. as the “ü” is not in the standard ASCII character set.
It’s meant to be used when there are potentially non-ASCII characters. An example might be when using data from a database to create a hyperlink. Suppose the code creates a link to a user profile page. Unencoded, mine would be:
while Günter’s would be
Mine, most browsers could handle. Günter’s, probably not.
Encoded, these would become
and
which are valid URLs.
(Please forgive the fact that most well-designed systems wouldn’t pass a username in a parameter like that. This was just a sample to clarify the concept.)