When is url encoding required

The percent sign is used as an escape character. The ASCII value of space character in decimal is 32 , which when converted to hex comes out to be It can be transmitted as is. But the encoding is still valid as per the RFC. All the characters that are safe to be transmitted inside URLs are colored green in the table. Share on social media Facebook Twitter Linkedin Reddit.

Some characters are utilized by URLs for special use in defining their syntax. When these characters are not used in their special role inside a URL, they must be encoded.

Some characters present the possibility of being misunderstood within URLs for various reasons. These characters should also always be encoded. As N-able Technologies allows and, in fact, encourages users to utilize 'special characters' in their passwords, the foreseeable problem arises when these values are passed as part of a URL string. Why do you need to encode URL? A URL is composed of only a limited number of characters and those are digits , letters A-Z, a-z , and a few special characters "-", ".

So does it mean that we cannot use any other character? The answer to this question is "YES". So if you want to transmit any character which is not a member of the above mentioned digits, letters, and special chars , then we need to encode them.

Is this enough for URL encoding? No this is not enough, there's a lot about URL encoding but here, I'm not gonna make it a pretty big, boring technical answer. Well, you do so because every different browsers knows how the string that makes up the URL is encoded. It could be latin-1 it could be unicode. It needs normalized to something that is understood universally.

Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Why do you need to encode URLs? Ask Question.

Asked 11 years, 9 months ago. Active 1 year ago. Viewed 32k times. Improve this question. Brian Brian