This software can decode Escaped-encoding, which uses a triplet sequence of "%", followed by two hexadecimal digits to represent the original character's octet code.
This software is designed to decode the Escaped-encoding URL. Escaped-encoding, sometimes referred to as percent-encoding, is the standard method used to represent characters within a URI that may require special handling in order to be properly interpreted. Essentially, it uses a sequence of three characters to encode the character to be interpreted. The triplet sequence consists of the percentage character “%” followed by the two hexadecimal digits representing the octet code of the original character.
For instance, the US-ASCII character set represents a space with octet code 32 or hexadecimal 20, thus its URL-encoded representation is %20. Applications may automatically escape reserved and unreserved characters, or automatically un-escape an escape-encoded sequence within a URI, if there is potential for it to be incorrectly interpreted by the remote application.
This conversion might be due to the position of the character or escape-encoded sequence in the URI. An example is "%7e," which is sometimes used instead of "~" in an http URL path. Still, they are equivalent for an http URL. Because the percent "%" character always has the reserved purpose of being the escape indicator, it must be escaped as "%25" to be used as data within a URI.
The RFC for URI encoding advises being cautious not to escape or un-escape the same string more than once, since un-escaping an already un-escaped string could misinterpret a percent data character as another escaped character or vice versa in the case of escaping an already escaped string.
The software is handy in decoding URLs and providing a useful list of escape codes for characters such as SPACE, <, >, #, %, {, }, |, \, ^, ~, [, ], `, ;, /, ?, :, @, =, &, and $.
For instance, the US-ASCII character set represents a space with octet code 32 or hexadecimal 20, thus its URL-encoded representation is %20. Applications may automatically escape reserved and unreserved characters, or automatically un-escape an escape-encoded sequence within a URI, if there is potential for it to be incorrectly interpreted by the remote application.
This conversion might be due to the position of the character or escape-encoded sequence in the URI. An example is "%7e," which is sometimes used instead of "~" in an http URL path. Still, they are equivalent for an http URL. Because the percent "%" character always has the reserved purpose of being the escape indicator, it must be escaped as "%25" to be used as data within a URI.
The RFC for URI encoding advises being cautious not to escape or un-escape the same string more than once, since un-escaping an already un-escaped string could misinterpret a percent data character as another escaped character or vice versa in the case of escaping an already escaped string.
The software is handy in decoding URLs and providing a useful list of escape codes for characters such as SPACE, <, >, #, %, {, }, |, \, ^, ~, [, ], `, ;, /, ?, :, @, =, &, and $.
What's New
Version 1.0: N/A