urlencode与rawurlencode? [英] urlencode vs rawurlencode?

问题描述

如果我想使用变量创建URL，我有两种选择来编码字符串. urlencode()和rawurlencode().

到底有什么区别，哪个是首选?

解决方案

这取决于您的目的.如果与其他系统的互操作性很重要，那么rawurlencode似乎是必经之路.一个例外是传统系统，该系统希望查询字符串遵循以+而不是％20(在这种情况下需要urlencode)编码的空格的表单编码样式.

rawurlencode 遵循PHP 5.3.0之前的RFC 1738，之后遵循RFC 3986(请参见 RFC 1866 中的application/x-www-form-urlencode的定义相对应. a>.

其他阅读内容:

您可能还希望在 http://bytes.com上查看讨论. /groups/php/5624-urlencode-vs-rawurlencode .

此外， RFC 2396 也值得一看. RFC 2396定义了有效的URI语法.我们感兴趣的主要部分来自3.4查询组件:

在查询组件中，字符";", "/", "?", ":", "@",
"&", "=", "+", ",", and "$"被保留.

如您所见，+是查询字符串中的保留字符，因此需要根据RFC 3986(如rawurlencode)进行编码.

If I want to create a URL using a variable I have two choices to encode the string. urlencode() and rawurlencode().

What exactly are the differences and which is preferred?

解决方案

It will depend on your purpose. If interoperability with other systems is important then it seems rawurlencode is the way to go. The one exception is legacy systems which expect the query string to follow form-encoding style of spaces encoded as + instead of %20 (in which case you need urlencode).

rawurlencode follows RFC 1738 prior to PHP 5.3.0 and RFC 3986 afterwards (see http://us2.php.net/manual/en/function.rawurlencode.php)

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 on RFC 3986 vs 1738. rawurlencode prior to php 5.3 encoded the tilde character (~) according to RFC 1738. As of PHP 5.3, however, rawurlencode follows RFC 3986 which does not require encoding tilde characters.

urlencode encodes spaces as plus signs (not as %20 as done in rawurlencode)(see http://us2.php.net/manual/en/function.urlencode.php)

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 application/x-www-form-urlencoded media type. This differs from the » RFC 3986 encoding (see rawurlencode()) in that for historical reasons, spaces are encoded as plus (+) signs.

This corresponds to the definition for application/x-www-form-urlencoded in RFC 1866.

Additional Reading:

You may also want to see the discussion at http://bytes.com/groups/php/5624-urlencode-vs-rawurlencode.

Also, RFC 2396 is worth a look. RFC 2396 defines valid URI syntax. The main part we're interested in is from 3.4 Query Component:

Within a query component, the characters ";", "/", "?", ":", "@",
"&", "=", "+", ",", and "$" are reserved.

As you can see, the + is a reserved character in the query string and thus would need to be encoded as per RFC 3986 (as in rawurlencode).

这篇关于urlencode与rawurlencode?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！