setcookie
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.
add a note
User Contributed Notessetrawcookie
lgb
01-Oct-2009 03:53
01-Oct-2009 03:53
Anonymous
10-Apr-2008 04:01
10-Apr-2008 04:01
For PHP 4 systems you can use...
<?php
header('Set-Cookie: name=value');
?>
... but it seems to be difficult to obtain the results without PHP's automatic URL decoding :o(
subs at voracity dot org
12-Dec-2006 07:31
12-Dec-2006 07:31
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().
Brian
10-Mar-2006 01:56
10-Mar-2006 01:56
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.