Why should i urlencode

Example 2 rawurlencode example 2. Submit a Pull Request Report a Bug. Parameters string The URL to be encoded. All the given characters are converted!

Currently this usage has only been allowed in the hostname part, but there are some proposals to allow such use in some URL schemes. Note also that some characters are currently "reserved" but should have instead been considered as "unsafe": this includes the parenthesis " " which are clearly unsafe when a URL is used in MIME headers.

The ['fragment'] part of a parsed URL after the first ' ' separator found in any URL must not be encoded with this rawurlencode function but instead by urlencode. The next thing to do is to check the URL scheme that you want to support for example, only 'http', 'https', or 'ftp'.

You may wich to check the ['port'] part to see if it's really a decimal integer between 1 and You may wish to remove the default port number used by the URL schemes you want to support for example the port '80' for 'http', the port '21' for 'ftp', the port '' for 'https' , and restrict severely all port numbers below , or some critical ports below this includes DNS and NetBios ports. Then you may wish to control severely the ['host'] part in fact a full host domain name or an IP address , by forbidding those host names that don't contain at least one dot, forbidding those that start with a dot, those that contain two consecutive dots, those that start or finish with a '-' dash, those that contain '.

This done, you must use the urlencode function on all parts up to the exploded path elements, and rawurlencode on the query and fragment parts, according to the specs, to recreate a complete and validated URL. In that case, these non compliant HTTP server will not find the resource associated to that URL and may return a error or other errors such as an access denied.

The encoding of host names uses another encoding, required to encode international domain names, with a base encoding of Unicode characters and a "bq--" prefix. This encoding must be used only on individual subdomain parts separated by ". Some parts of the URL syntax like [user:password ] are deprecated and seldom used due to security reasons. Following is an example of a URL that you see more often on the internet -. This post contains information from the latest RFC document. These characters include digits , letters A-Z, a-z , and a few special characters "-" , ".

ASCII control characters e. Moreover, there are some characters that have special meaning within URLs. Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4. For details, see the Google Developers Site Policies. Routes Directions API. Places Places API. Additional Resources.

Conforming a URL to use this set of characters generally leads to two issues, one of omission and one of substitution: Characters that you wish to handle exist outside of the above set.