$str
)
Encodes the given string according to » RFC 3986.
Anonymous user / 18.226.200.221 Log In Register |
?
Wallet:
3.00
Daily Credits:
1.20 / 1.20
|
This is your credit balance. Even if you are an anonymous user, you are given some credits to spend. Every IP address has its own account and it is provided with free credits that can be used to pay for Online Domain Tools services. Moreover, credit balance is reset every day. This is why we call them Daily Credits. Registered users have higher Daily Credits amounts and can even increase them by purchasing subscriptions.
Besides Daily Credits, all accounts, including IP address accounts of anonymous users, have their credit Wallet. Wallet credits are not reset on a daily basis, but they are only spent when a user has not enough Daily Credits. Registered users can buy credits to their wallets. All IP address accounts are created with an initial Wallet balance of 3.00. Once IP address account spends credits from its Wallet, it can not be charged again. This should allow new users to try most of Online Domain Tools services without registration.
$str
)
Encodes the given string according to » RFC 3986.
The URL to be encoded.
Returns a string in which all non-alphanumeric characters except -_.~ have been replaced with a percent (%) sign followed by two hex digits. This is the encoding described in » RFC 3986 for protecting literal characters from being interpreted as special URL delimiters, and for protecting URLs from being mangled by transmission media with character conversions (like some email systems).
Note:
Prior to PHP 5.3.0, rawurlencode encoded tildes (~) as per » RFC 1738.
Example #1 including a password in an FTP URL
<?php
echo '<a href="http://www.php.net/manual/en/ftp://user:', rawurlencode('foo @+%/'),
'@ftp.example.com/x.txt">';
?>
The above example will output:
<a href="ftp://user:foo%20%40%2B%25%2F@ftp.example.com/x.txt">
Version | Description |
---|---|
5.3.4 | Tilde characters are no longer encoded when rawurlencode() is used with EBCDIC strings. |
5.3.0 | Now conforms to » RFC 3986. |