Why url encoding is required

Viewed 32k times. Improve this question. Brian Brian Add a comment. Active Oldest Votes. Because some characters have special meanings. Improve this answer. Jim Jim It still would look like the separator between key-val pairs isn't it??

From RFC , section 2. Ignacio Vazquez-Abrams Ignacio Vazquez-Abrams k gold badges silver badges bronze badges. In other words, "No, there's not an inherent technical reason but we know implementors and users are both sloppy. Matthew - There is a inherent technical reason, see my answer — Rippo. Rippo: Your answer claims that they are "unsafe", but does not give any technical reason why. Matthew - In my experience unsafe means that there must be a technical reason Show 3 more comments.

You will see later where these numbers come from. As a rule of thumb, any non alphanumeric character should be URL encoded. This of course applies to characters that are to be interpreted as is ie: is not intend to have special meanings. Where Does the Numbers Come From? This article will take advantage of inbuilt functions and encode method of java. A Uniform Resource Identifier URI is a compact sequence of characters that identifies an abstract or physical resource.

A URL is a URI that, in addition to identifying a web resource, specifies the means of acting upon or obtaining the representation, specifying both its primary access mechanism and network location. While it is possible to load documents into MarkLogic Server, where the document URI contains special characters not encoded, it is recommended to follow best practices by URL encoding document URIs as it will help you design robust applications, free from the side effects caused by such special characters in other areas of your application stack.

For instance, the " " character needs to be encoded because it has a special meaning of that of an html anchor. Consider the example where a parameter is supplied in a URL and parameter value has a special character in it, such as,. For URL specifications, there are various established standards including below listed w3c standards:. Object initializer Operator precedence Optional chaining?. Warning: JavaScript 1.