Why url encode, or which characters to encode

Question

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?

UTF-8 characters for example, or any character from a different character set. ASCII is just about the smallest range of characters. — Halcyon
I'm not shure, but I think every character should be encoded which could have a different meaning (for example & and space). Dont use w3schools.com, it has nothing to do with w3c and is quite often wrong. — user1150525

David David · Accepted Answer · 2012-01-31T20:27:24

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:

<a href="profile/?username=David Stratton">Your profile</a>

while Günter's would be

<a href="profile/?username=Günter">Your profile</a>

Mine, most browsers could handle. Günter's, probably not.

Encoded, these would become

<a href="profile/?username=David%20Stratton">Your profile</a>

and

<a href="profile/?username=G%FCnter">Your profile</a>

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.)

Why url encode, or which characters to encode

4 Answers