# Metadata
Platforms: desktop, server, mobile OS: mac, windows, linux, ios, android Introduced: 1.0 Security: network
# Syntax
the URLEncode of formString
# Params
- formString :
# Examples
URLEncode("ABC123") -- returns "ABC123"
URLEncode("Test string $$") -- returns "Test+string+%24%24"
local tGoodURL put "http://www.example.net/" & URLEncode("A File Name with spaces.html") into tGoodURL
# Description
Letters and numbers (alphanumeric characters) are not transformed by the URLEncode function. The representation used for non-alphanumeric characters is a percent sign followed by two hexadecimal digits. For example, the ASCII of the character ~ is 126; the hexadecimal equivalent of 126 is 7E. So wherever the character ~ appears in the formString, it is converted to "%7E".
>*Note:* The URLEncode function does not conform to RFC3986. In order > to produce a string that does conform to it, you would first encode > the string to UTF-8 and then after performing URLEncode, replace all > instances of "+" with "%20". For example:
function urlEncodeRFC pString if pString is strictly a string then put textEncode(pString,"UTF-8") into pString end if put URLEncode(pString) into pString replace "+" with "%20" in pString return pString end urlEncodeRFC
>*Note:* Non-ASCII characters, such as Unicode, that appear in the string > to be encoded must first be encoded as UTF-8 (as per standard > convention), requiring the use of the textEncode function. > The code example given above can perform this task.
# Tags
# See