setrawcookie

(PHP 5)

setrawcookie — Send a cookie without urlencoding the cookie value

说明

bool setrawcookie ( string $name [, string $value [, int $expire = 0 [, string $path [, string $domain [, bool $secure = false [, bool $httponly = false ]]]]]] )

setrawcookie() is exactly the same as setcookie() except that the cookie value will not be automatically urlencoded when sent to the browser.

参数

For parameter information, see the setcookie() documentation.

返回值

成功时返回 TRUE ，或者在失败时返回 FALSE 。

更新日志

版本	说明
5.5.0	A Max-Age attribute is now included in the Set-Cookie header sent to the client.
5.2.0	The `httponly` parameter was added.

参见

setcookie() - Send a cookie

用户评论:

[#1] sageptr at gmail dot com [2012-07-16 16:10:58]

If you want to pass something and unserialize later, you should somehow sign value to ensure evil user don't modify it.
For example, calculate hash sha1($value.$securekey) and place it to different cookie. If cookie value mismatch hash - simple discard both.
This technique you can use in any case if you want to protect cookie from modification, but it can't protect from deletion or from setting to other valid cookie (old or stolen from other user).

[#2] kexianbin at diyism dot com [2011-12-28 19:35:46]

my php cookie value encode function:

<?php function encode_cookie_value($value) {return strtr($value, array_combine(str_split($tmp=",; \t\r\n\013\014"), array_map('rawurlencode', str_split($tmp)) ) ); } setrawcookie('kk', encode_cookie_value('jk=jk?jk-/":jk;jk jk,jk')); ?>

[#3] Sebastian [2011-06-29 04:59:47]

You really shouldn't use (un)serialize with cookies. An evil user could inject ANY code in your script.

[#4] lgb [2009-10-01 01:53:08]

After having several problems with this cookie thing, I'm using base64_encode on the data I put into a cookie, so I can avoid problems, I had before. I tried to set up cookie with data created by serialize() from a PHP array, but it did not work to be able to get it back, after I modified it to use value of base64_encode(serialize(...)) to set up the cookie, and unserialize(base64_decode(..)) to get back the value, everything started to work.

[#5] subs at voracity dot org [2006-12-12 05:31:53]

setrawcookie() isn't entirely 'raw'. It will check the value for invalid characters, and then disallow the cookie if there are any. These are the invalid characters to keep in mind: ',;<space>\t\r\n\013\014'.

Note that comma, space and tab are three of the invalid characters. IE, Firefox and Opera work fine with these characters, and PHP reads cookies containing them fine as well. However, if you want to use these characters in cookies that you set from php, you need to use header().

[#6] Brian [2006-03-10 11:56:39]

Firefox is following the real spec and does not decode '+' to space...in fact it further encodes them to '%2B' to store the cookie. If you read a cookie using javascript and unescape it, all your spaces will be turned to '+'.
To fix this problem, use setrawcookie and rawurlencode:

<?php setrawcookie('cookie_name', rawurlencode($value), time()+60*60*24*365); ?>

The only change is that spaces will be encoded to '%20' instead of '+' and will now decode properly.