Elettracompany.com

Компьютерный справочник
0 просмотров
Рейтинг статьи
1 звезда2 звезды3 звезды4 звезды5 звезд
Загрузка...

Url decode php

urldecode

(PHP 4, PHP 5, PHP 7)

urldecode — Декодирование URL-кодированной строки

Описание

Декодирует любые кодированные последовательности % ## в данной строке. Символ «плюс» (‘+‘) декодируется в символ пробела.

Список параметров

Строка, которая должна быть декодирована.

Возвращаемые значения

Возвращает декодированную строку.

Примеры

Пример #1 Пример использования urldecode()

Примечания

Переменные в суперглобальных массивах $_GET и $_REQUEST уже декодированы. Применение urldecode() к элементам $_GET или $_REQUEST может привести к неожиданным и опасным результатам.

Смотрите также

  • urlencode() — URL-кодирование строки
  • rawurlencode() — URL-кодирование строки согласно RFC 3986
  • rawurldecode() — Декодирование URL-кодированной строки
  • » RFC 3986

User Contributed Notes 19 notes

When the client send Get data, utf-8 character encoding have a tiny problem with the urlencode.
Consider the «º» character.
Some clients can send (as example)
foo.php?myvar=%BA
and another clients send
foo.php?myvar=%C2%BA (The «right» url encoding)

in this scenary, you assign the value into variable $x

$x store: in the first case «�» (bad) and in the second case «º» (good)

To fix that, you can use this function:

and assign in this way:

$x store: in the first case «º» (good) and in the second case «º» (good)

Solve a lot of i18n problems.

Please fix the auto-urldecode of $_GET var in the next PHP version.

mkaganer at gmail dot com:

try using encodeURI() instead of encode() in javascript. That worked for me, while your solution did not on __some__ national characters (at least in IE6).

A reminder: if you are considering using urldecode() on a $_GET variable, DON’T!

The webserver will arrange for $_GET to have been urldecoded once already by the time it reaches you!

Using urldecode() on $_GET can lead to extreme badness, PARTICULARLY when you are assuming «magic quotes» on GET is protecting you against quoting.

PHP «receives» this as %27, which your urldecode() will convert to «‘» (the singlequote). This may be CATASTROPHIC when injecting into SQL or some PHP functions relying on escaped quotes — magic quotes rightly cannot detect this and will not protect you!

This «common error» is one of the underlying causes of the Santy.A worm which affects phpBB

This function doesn’t decode unicode characters. I wrote a function that does.

function unicode_urldecode($url)
<
preg_match_all(‘/%u([[:alnum:]]<4>)/’, $url, $a);

foreach ($a[1] as $uniord)
<
$dec = hexdec($uniord);
$utf = »;

When sending a string via AJAX POST data which contains an ampersand (&), be sure to use encodeURIComponent() on the javascript side and use urldecode() on the php side for whatever variable that was. I’ve found it tricky to transfer raw ampersands and so this is what worked for me:
«one & two»

?>
For some reason, a variable with an ampersand would stay encoded while other POST variables were automatically decoded. I concatenated data from an html form before submitting, in case you wish to know what happened on the browser end.

For compatibility of new and old brousers:

%xx -> char
%u0xxxx -> char

function unicode_decode($txt) <
$txt = ereg_replace(‘%u0([[:alnum:]]<3>)’, ‘’,$txt);
$txt = ereg_replace(‘%([[:alnum:]]<2>)’, ‘’,$txt);
return ($txt);
>

It’s worth pointing out that if you are using AJAX and need to encode strings that are being sent to a PHP application, you may not need to decode them in PHP.

Will properly output a message sent with the javascript code if the message is encoded:

And is sent with an AJAX POST request with the header:
ajaxVar.setRequestHeader(‘Content-type’, ‘application/x-www-form-urlencoded’)

I had troubles converting Unicode-encoded data in $_GET (like this: %u05D8%u05D1%u05E2) which is generated by JavaScript’s escape() function to UTF8 for server-side processing.

Finally, i’ve found a simple solution (only 3 lines of code) that does it (at least in my configuration):

note that documentation for html_entity_decode() states that «Support for multi-byte character sets was added at PHP 5.0.0» so this might not work for PHP 4

urldecode does not decode «%0» bypassing it. I can cause troble when you are working with fixed lenght strings.

You can you the function below.

$array = split («%»,$string);

if (is_array($array)) <
while (list ($k,$v) = each ($array)) <
$ascii = base_convert ($v,16,10);
$ret .= chr ($ascii);
>
>
return («$ret»);
>

It seems that the $_REQUEST global parameter is automatically decoded only if the content type is application/x-www-form-urlencoded.

if the content type is multipart/form-data. the data remains un-decoded. and we have to manually handle the decoding at our end

nataniel, your function needs to be corrected as follows:

since some codes does not begin with %u0.

If you have a «html reserved word» as variable name (i.e. «reg_var») and you pass it as an argument you will get a wrong url. i.e.

you will get a wrong url like this

Simply add a space between «&» and «reg_var» and it will work!

About reg_var and «html reserved words»

Do not add spaces as the user suggests.

Instead, do what all HTML standards says and encode & in URLs as & in your HTML.

The reason why & works «most of the time» is that browsers are forgiving and just decode the & as the &-sign. This breaks whenever you have a variable that matches an HTML entity, like «gt» or «copy» or whatever. &copy in your URL will be interpreted as © (the ; is not mandatory in SGML as it is «implied». In XML it is mandatory.). The result will be the same as if you had inserted the actual character into your source code, for instance by pressing alt-0169 and actually inserted � in your HTML.

Note that the decoding of & to & is done in the browser, and it’s done right after splitting the HTML into tags, attributes and content, but it works both for attributes and content.

This mean you should &entitify all &-s in any other HTML attributes as well, such as in a form with
.

This seems to decode correctly between most browsers and charater coding configurations. Specially indicated for direct parsing of URL as it comes on environment variables:

function crossUrlDecode($source) <
$decodedStr = »;
$pos = 0;
$len = strlen($source);

while ($pos 127) <
$decodedStr .= «&#».ord($charAt).»;»;
$pos++;
>
elseif($charAt == ‘%’) <
$pos++;
$hex2 = substr($source, $pos, 2);
$dechex = chr(hexdec($hex2));
if($dechex == ‘�’) <
$pos += 2;
if(substr($source, $pos, 1) == ‘%’) <
$pos++;
$char2a = chr(hexdec(substr($source, $pos, 2)));
$decodedStr .= htmlentities(utf8_decode($dechex . $char2a),ENT_QUOTES,’ISO-8859-1′);
>
else <
$decodedStr .= htmlentities(utf8_decode($dechex));
>
>
else <
$decodedStr .= $dechex;
>
$pos += 2;
>
else <
$decodedStr .= $charAt;
$pos++;
>
>

Send json to PHP via AJAX (POST)

If you send json data via ajax, and encode it with encodeURIComponent in javascript, then on PHP side, you will have to do stripslashes on your $_POST[‘myVar’].

After this, you can do json_decode on your string.

urldecode

(PHP 4, PHP 5, PHP 7)

urldecode — Декодирование URL-кодированной строки

Описание

Декодирует любые кодированные последовательности % ## в данной строке. Символ «плюс» (‘+‘) декодируется в символ пробела.

Читать еще:  Php fopen utf 8

Список параметров

Строка, которая должна быть декодирована.

Возвращаемые значения

Возвращает декодированную строку.

Примеры

Пример #1 Пример использования urldecode()

Примечания

Переменные в суперглобальных массивах $_GET и $_REQUEST уже декодированы. Применение urldecode() к элементам $_GET или $_REQUEST может привести к неожиданным и опасным результатам.

Смотрите также

  • urlencode() — URL-кодирование строки
  • rawurlencode() — URL-кодирование строки согласно RFC 3986
  • rawurldecode() — Декодирование URL-кодированной строки
  • » RFC 3986

User Contributed Notes 19 notes

When the client send Get data, utf-8 character encoding have a tiny problem with the urlencode.
Consider the «º» character.
Some clients can send (as example)
foo.php?myvar=%BA
and another clients send
foo.php?myvar=%C2%BA (The «right» url encoding)

in this scenary, you assign the value into variable $x

$x store: in the first case «�» (bad) and in the second case «º» (good)

To fix that, you can use this function:

and assign in this way:

$x store: in the first case «º» (good) and in the second case «º» (good)

Solve a lot of i18n problems.

Please fix the auto-urldecode of $_GET var in the next PHP version.

mkaganer at gmail dot com:

try using encodeURI() instead of encode() in javascript. That worked for me, while your solution did not on __some__ national characters (at least in IE6).

A reminder: if you are considering using urldecode() on a $_GET variable, DON’T!

The webserver will arrange for $_GET to have been urldecoded once already by the time it reaches you!

Using urldecode() on $_GET can lead to extreme badness, PARTICULARLY when you are assuming «magic quotes» on GET is protecting you against quoting.

PHP «receives» this as %27, which your urldecode() will convert to «‘» (the singlequote). This may be CATASTROPHIC when injecting into SQL or some PHP functions relying on escaped quotes — magic quotes rightly cannot detect this and will not protect you!

This «common error» is one of the underlying causes of the Santy.A worm which affects phpBB

This function doesn’t decode unicode characters. I wrote a function that does.

function unicode_urldecode($url)
<
preg_match_all(‘/%u([[:alnum:]]<4>)/’, $url, $a);

foreach ($a[1] as $uniord)
<
$dec = hexdec($uniord);
$utf = »;

When sending a string via AJAX POST data which contains an ampersand (&), be sure to use encodeURIComponent() on the javascript side and use urldecode() on the php side for whatever variable that was. I’ve found it tricky to transfer raw ampersands and so this is what worked for me:
«one & two»

?>
For some reason, a variable with an ampersand would stay encoded while other POST variables were automatically decoded. I concatenated data from an html form before submitting, in case you wish to know what happened on the browser end.

For compatibility of new and old brousers:

%xx -> char
%u0xxxx -> char

function unicode_decode($txt) <
$txt = ereg_replace(‘%u0([[:alnum:]]<3>)’, ‘’,$txt);
$txt = ereg_replace(‘%([[:alnum:]]<2>)’, ‘’,$txt);
return ($txt);
>

It’s worth pointing out that if you are using AJAX and need to encode strings that are being sent to a PHP application, you may not need to decode them in PHP.

Will properly output a message sent with the javascript code if the message is encoded:

And is sent with an AJAX POST request with the header:
ajaxVar.setRequestHeader(‘Content-type’, ‘application/x-www-form-urlencoded’)

I had troubles converting Unicode-encoded data in $_GET (like this: %u05D8%u05D1%u05E2) which is generated by JavaScript’s escape() function to UTF8 for server-side processing.

Finally, i’ve found a simple solution (only 3 lines of code) that does it (at least in my configuration):

note that documentation for html_entity_decode() states that «Support for multi-byte character sets was added at PHP 5.0.0» so this might not work for PHP 4

urldecode does not decode «%0» bypassing it. I can cause troble when you are working with fixed lenght strings.

You can you the function below.

$array = split («%»,$string);

if (is_array($array)) <
while (list ($k,$v) = each ($array)) <
$ascii = base_convert ($v,16,10);
$ret .= chr ($ascii);
>
>
return («$ret»);
>

It seems that the $_REQUEST global parameter is automatically decoded only if the content type is application/x-www-form-urlencoded.

if the content type is multipart/form-data. the data remains un-decoded. and we have to manually handle the decoding at our end

nataniel, your function needs to be corrected as follows:

since some codes does not begin with %u0.

If you have a «html reserved word» as variable name (i.e. «reg_var») and you pass it as an argument you will get a wrong url. i.e.

you will get a wrong url like this

Simply add a space between «&» and «reg_var» and it will work!

About reg_var and «html reserved words»

Do not add spaces as the user suggests.

Instead, do what all HTML standards says and encode & in URLs as & in your HTML.

The reason why & works «most of the time» is that browsers are forgiving and just decode the & as the &-sign. This breaks whenever you have a variable that matches an HTML entity, like «gt» or «copy» or whatever. &copy in your URL will be interpreted as © (the ; is not mandatory in SGML as it is «implied». In XML it is mandatory.). The result will be the same as if you had inserted the actual character into your source code, for instance by pressing alt-0169 and actually inserted � in your HTML.

Note that the decoding of & to & is done in the browser, and it’s done right after splitting the HTML into tags, attributes and content, but it works both for attributes and content.

This mean you should &entitify all &-s in any other HTML attributes as well, such as in a form with
.

This seems to decode correctly between most browsers and charater coding configurations. Specially indicated for direct parsing of URL as it comes on environment variables:

function crossUrlDecode($source) <
$decodedStr = »;
$pos = 0;
$len = strlen($source);

while ($pos 127) <
$decodedStr .= «&#».ord($charAt).»;»;
$pos++;
>
elseif($charAt == ‘%’) <
$pos++;
$hex2 = substr($source, $pos, 2);
$dechex = chr(hexdec($hex2));
if($dechex == ‘�’) <
$pos += 2;
if(substr($source, $pos, 1) == ‘%’) <
$pos++;
$char2a = chr(hexdec(substr($source, $pos, 2)));
$decodedStr .= htmlentities(utf8_decode($dechex . $char2a),ENT_QUOTES,’ISO-8859-1′);
>
else <
$decodedStr .= htmlentities(utf8_decode($dechex));
>
>
else <
$decodedStr .= $dechex;
>
$pos += 2;
>
else <
$decodedStr .= $charAt;
$pos++;
>
>

Send json to PHP via AJAX (POST)

If you send json data via ajax, and encode it with encodeURIComponent in javascript, then on PHP side, you will have to do stripslashes on your $_POST[‘myVar’].

After this, you can do json_decode on your string.

urldecode

(PHP 4, PHP 5, PHP 7)

urldecode — Декодирование URL-кодированной строки

Описание

Декодирует любые % ## кодированные последовательности в данной строке. Символ «плюс» (‘+‘) декодируется в символ пробела.

Список параметров

Строка, которая должны быть декодирована.

Возвращаемые значения

Возвращает декодированную строку.

Читать еще:  Команды в matlab

Примеры

Пример #1 Пример использования urldecode()

Примечания

Переменные в суперглобальных массивах $_GET и $_REQUEST уже декодированы. Применение urldecode() к элементам $_GET или $_REQUEST может привести к непредсказуемым и опасным результатам.

Смотрите также

  • urlencode() — URL-кодирование строки
  • rawurlencode() — URL-кодирование строки согласно RFC 3986
  • rawurldecode() — Декодирование URL-кодированной строки
  • » RFC 3986

Коментарии

This seems to decode correctly between most browsers and charater coding configurations. Specially indicated for direct parsing of URL as it comes on environment variables:

function crossUrlDecode($source) <
$decodedStr = »;
$pos = 0;
$len = strlen($source);

while ($pos 127) <
$decodedStr .= «&#».ord($charAt).»;»;
$pos++;
>
elseif($charAt == ‘%’) <
$pos++;
$hex2 = substr($source, $pos, 2);
$dechex = chr(hexdec($hex2));
if($dechex == ‘�’) <
$pos += 2;
if(substr($source, $pos, 1) == ‘%’) <
$pos++;
$char2a = chr(hexdec(substr($source, $pos, 2)));
$decodedStr .= htmlentities(utf8_decode($dechex . $char2a),ENT_QUOTES,’ISO-8859-1′);
>
else <
$decodedStr .= htmlentities(utf8_decode($dechex));
>
>
else <
$decodedStr .= $dechex;
>
$pos += 2;
>
else <
$decodedStr .= $charAt;
$pos++;
>
>

For compatibility of new and old brousers:

%xx -> char
%u0xxxx -> char

function unicode_decode($txt) <
$txt = ereg_replace(‘%u0([[:alnum:]]<3>)’, ‘’,$txt);
$txt = ereg_replace(‘%([[:alnum:]]<2>)’, ‘’,$txt);
return ($txt);
>

If you have a «html reserved word» as variable name (i.e. «reg_var») and you pass it as an argument you will get a wrong url. i.e.

you will get a wrong url like this

Simply add a space between «&» and «reg_var» and it will work!

urldecode does not decode «%0» bypassing it. I can cause troble when you are working with fixed lenght strings.

You can you the function below.

$array = split («%»,$string);

if (is_array($array)) <
while (list ($k,$v) = each ($array)) <
$ascii = base_convert ($v,16,10);
$ret .= chr ($ascii);
>
>
return («$ret»);
>

nataniel, your function needs to be corrected as follows:

since some codes does not begin with %u0.

To allow urldecode to work with Brazilian characters as � � � and other just place this header command :

header(‘Content-type: text/html; charset=UTF-8’);

A reminder: if you are considering using urldecode() on a $_GET variable, DON’T!

The webserver will arrange for $_GET to have been urldecoded once already by the time it reaches you!

Using urldecode() on $_GET can lead to extreme badness, PARTICULARLY when you are assuming «magic quotes» on GET is protecting you against quoting.

PHP «receives» this as %27, which your urldecode() will convert to «‘» (the singlequote). This may be CATASTROPHIC when injecting into SQL or some PHP functions relying on escaped quotes — magic quotes rightly cannot detect this and will not protect you!

This «common error» is one of the underlying causes of the Santy.A worm which affects phpBB

About reg_var and «html reserved words»

Do not add spaces as the user suggests.

Instead, do what all HTML standards says and encode & in URLs as & in your HTML.

The reason why & works «most of the time» is that browsers are forgiving and just decode the & as the &-sign. This breaks whenever you have a variable that matches an HTML entity, like «gt» or «copy» or whatever. &copy in your URL will be interpreted as © (the ; is not mandatory in SGML as it is «implied». In XML it is mandatory.). The result will be the same as if you had inserted the actual character into your source code, for instance by pressing alt-0169 and actually inserted � in your HTML.

Note that the decoding of & to & is done in the browser, and it’s done right after splitting the HTML into tags, attributes and content, but it works both for attributes and content.

This mean you should &entitify all &-s in any other HTML attributes as well, such as in a form with
.

This function doesn’t decode unicode characters. I wrote a function that does.

function unicode_urldecode($url)
<
preg_match_all(‘/%u([[:alnum:]]<4>)/’, $url, $a);

foreach ($a[1] as $uniord)
<
$dec = hexdec($uniord);
$utf = »;

I had troubles converting Unicode-encoded data in $_GET (like this: %u05D8%u05D1%u05E2) which is generated by JavaScript’s escape() function to UTF8 for server-side processing.

Finally, i’ve found a simple solution (only 3 lines of code) that does it (at least in my configuration):

note that documentation for html_entity_decode() states that «Support for multi-byte character sets was added at PHP 5.0.0» so this might not work for PHP 4

It’s worth pointing out that if you are using AJAX and need to encode strings that are being sent to a PHP application, you may not need to decode them in PHP.

Will properly output a message sent with the javascript code if the message is encoded:

And is sent with an AJAX POST request with the header:
ajaxVar.setRequestHeader(‘Content-type’, ‘application/x-www-form-urlencoded’)

mkaganer at gmail dot com:

try using encodeURI() instead of encode() in javascript. That worked for me, while your solution did not on __some__ national characters (at least in IE6).

Send json to PHP via AJAX (POST)

If you send json data via ajax, and encode it with encodeURIComponent in javascript, then on PHP side, you will have to do stripslashes on your $_POST[‘myVar’].

After this, you can do json_decode on your string.

When the client send Get data, utf-8 character encoding have a tiny problem with the urlencode.
Consider the «º» character.
Some clients can send (as example)
foo.php?myvar=%BA
and another clients send
foo.php?myvar=%C2%BA (The «right» url encoding)

in this scenary, you assign the value into variable $x

$x store: in the first case «�» (bad) and in the second case «º» (good)

To fix that, you can use this function:

and assign in this way:

$x store: in the first case «º» (good) and in the second case «º» (good)

Solve a lot of i18n problems.

Please fix the auto-urldecode of $_GET var in the next PHP version.

It seems that the $_REQUEST global parameter is automatically decoded only if the content type is application/x-www-form-urlencoded.

if the content type is multipart/form-data. the data remains un-decoded. and we have to manually handle the decoding at our end

When sending a string via AJAX POST data which contains an ampersand (&), be sure to use encodeURIComponent() on the javascript side and use urldecode() on the php side for whatever variable that was. I’ve found it tricky to transfer raw ampersands and so this is what worked for me:
«one & two»

?>
For some reason, a variable with an ampersand would stay encoded while other POST variables were automatically decoded. I concatenated data from an html form before submitting, in case you wish to know what happened on the browser end.

Decode from URL encoded format

Decode files from URL encoded format

About

Meet URL Decode and Encode, a simple online tool that does exactly what it says; decodes URL encoding and encodes into it quickly and easily. URL encode your data in a hassle-free way, or decode it into human-readable format.

Читать еще:  Fuzzy logic matlab

URL encoding, also known as percent-encoding, is a mechanism for encoding information in a Uniform Resource Identifier (URI) under certain circumstances. Although it is known as URL encoding it is, in fact, used more generally within the main Uniform Resource Identifier (URI) set, which includes both Uniform Resource Locator (URL) and Uniform Resource Name (URN). As such it is also used in the preparation of data of the «application/x-www-form-urlencoded» media type, as is often used in the submission of HTML form data in HTTP requests.

Advanced options

  • Character set: In case of textual data the encoding scheme does not contain their character set, so you have to specify which one was used during the encoding process. It is usually UTF-8, but can be any other; if you are not sure then play with the available options including the auto-detect one. This information is used to convert the decoded data into our website’s character set, so all letters and symbols can be displayed properly. Note that this is irrelevant for files, since no web-safe conversions have to be applied to them.
  • Decode each line separately: The encoded data usually consist of continuous text, even newlines are converted into their percent encoded forms. Prior decoding all non-encoded whitespaces are stripped from the input to take care of its integrity. This option is useful if you intended to decode multiple independent data entries separated with line breaks.
  • Live mode: When you turn on this option the entered data is decoded immediately with your browser’s built-in JavaScript functions — without sending any information to our servers. Currently this mode supports only the UTF-8 character set.

Safe and secure

All communications with our servers are made through secure SSL encrypted connections (https). Uploaded files are deleted from our servers immediately after being processed, and the resulting downloadable file is deleted right after the first download attempt, or 15 minutes of inactivity. We do not keep or inspect the contents of the entered data or uploaded files in any way. Read our privacy policy below for more details.

Our tool is free to use. From now you don’t have to download any software for such tasks.

Details of the URL encoding

Types of URI characters

The characters allowed in a URI are either reserved or unreserved (or a percent character as part of a percent-encoding). Reserved characters are those characters that sometimes have special meaning. For example, forward slash characters are used to separate different parts of a URL (or more generally, a URI). Unreserved characters have no such meanings. Using percent-encoding, reserved characters are represented using special character sequences. The sets of reserved and unreserved characters and the circumstances under which certain reserved characters have special meaning have changed slightly with each revision of specifications that govern URIs and URI schemes.

Encode to URL encoded format

Encode files into URL encoded format

About

Meet URL Decode and Encode, a simple online tool that does exactly what it says; decodes URL encoding and encodes into it quickly and easily. URL encode your data in a hassle-free way, or decode it into human-readable format.

URL encoding, also known as percent-encoding, is a mechanism for encoding information in a Uniform Resource Identifier (URI) under certain circumstances. Although it is known as URL encoding it is, in fact, used more generally within the main Uniform Resource Identifier (URI) set, which includes both Uniform Resource Locator (URL) and Uniform Resource Name (URN). As such it is also used in the preparation of data of the «application/x-www-form-urlencoded» media type, as is often used in the submission of HTML form data in HTTP requests.

Advanced options

  • Character set: Our website uses UTF-8 character set, your input data is transmitted in that format. Change this option if you want to convert it into another one before encoding. Note that in case of textual data the encoding scheme does not contain their character set, so you may have to specify the selected one during the decoding process. As for files a binary option is the default, which will omit any conversion; this is required for everything except plain text documents.
  • Newline separator: Unix and Windows systems uses different line break characters, prior encoding either variants will be replaced within your data to the selected option. At the files section this is partially irrelevant since they contain intended versions, but you can define which one to use for the encode each line separately and split lines into chunks functions.
  • Encode each line separately: Even newline characters are converted to their percent encoded forms. Use this option if you want to encode multiple independent data entries separated with line breaks. (*)
  • Split lines into chunks: The encoded data will be a continuous text without any whitespaces, check this option if you want to break it up into multiple lines. The applied character limit is defined in the MIME (RFC 2045) specification, which states that the encoded lines must be no more than 76 characters long. (*)
  • Live mode: When you turn on this option the entered data is encoded immediately with your browser’s built-in JavaScript functions — without sending any information to our servers. Currently this mode supports only the UTF-8 character set.

(*) These options cannot be enabled simultaneously, since the resulting output would not be valid for the majority of applications.

Safe and secure

All communications with our servers are made through secure SSL encrypted connections (https). Uploaded files are deleted from our servers immediately after being processed, and the resulting downloadable file is deleted right after the first download attempt, or 15 minutes of inactivity. We do not keep or inspect the contents of the entered data or uploaded files in any way. Read our privacy policy below for more details.

Our tool is free to use. From now you don’t have to download any software for such tasks.

Details of the URL encoding

Types of URI characters

The characters allowed in a URI are either reserved or unreserved (or a percent character as part of a percent-encoding). Reserved characters are those characters that sometimes have special meaning. For example, forward slash characters are used to separate different parts of a URL (or more generally, a URI). Unreserved characters have no such meanings. Using percent-encoding, reserved characters are represented using special character sequences. The sets of reserved and unreserved characters and the circumstances under which certain reserved characters have special meaning have changed slightly with each revision of specifications that govern URIs and URI schemes.

Ссылка на основную публикацию
Adblock
detector