urlencode
urlencode
URL-encodes string
string **urlencode** string $string
This function is convenient when encoding a string to be used in a query part of a URL, as a convenient way to pass variables to the next page.
stringThe string 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 and spaces encoded
as plus () signs. It is encoded the same way that the
posted data from a WWW form is encoded, that is the same way as in
media type. This
differs from the encoding (see
) in that for historical reasons, spaces
are encoded as plus (+) signs.
-_.``%``+``application/x-www-form-urlencodedRFC 3986rawurlencode
Voorbeeld: example
<?php
$userinput = 'Data123!@-_ +';
echo "UserInput: $userinput\n";
echo '<a href="mycgi?foo=', urlencode($userinput), '">';
?>
UserInput: Data123!@-_ +
<a href="mycgi?foo=Data123%21%40-_+%2B">
Voorbeeld: and example
<?php
$foo = 'Data123!@-_ +';
$bar = "Not the same content as $foo";
echo "foo: $foo\n";
echo "bar: $bar\n";
$query_string = 'foo=' . urlencode($foo) . '&bar=' . urlencode($bar);
echo '<a href="mycgi?' . htmlentities($query_string) . '">';
?>
foo: Data123!@-_ +
bar: Not the same content as Data123!@-_ +
<a href="mycgi?foo=Data123%21%40-_+%2B&bar=Not+the+same+content+as+Data123%21%40-_+%2B">
Opmerking: > Be careful about variables that may match HTML entities. Things like &, © and £ are parsed by the browser and the actual entity is used instead of the desired variable name. This is an obvious hassle that the W3C has been telling people about for years. The reference is here: . url.argsep
PHP supports changing the argument separator to the W3C-suggested semi-colon through the arg_separator .ini directive. Unfortunately most user agents do not send form data in this semi-colon separated format. A more portable way around this is to use & instead of & as the separator. You don't need to change PHP's arg_separator for this. Leave it as &, but simply encode your URLs using or .
htmlentities``htmlspecialchars
urldecode``htmlentities``rawurlencode``rawurldecodeRFC 3986