note 52648 added to function.setcookie

A few comments have suggested using serialize() to set object or array data into a cookie. There are a couple of reasons to be carefull with that technique: Security: If the cookie is human readable, then it is also fairly easy for end users to play around with it. Wrapping your cookie setting and getting in an encryption routine will prevent tampering, and make sure that your cookies don't make any sense to any client-side exploits or other sites they get sent to thanks to browser bugs. Bulk: If you serialize even a fairly simple class, then you get a lot of data. Large cookies will make browser requests fat and slow, and some browsers have a limit on cookie size, so think about what data you really need to persist, and create __sleep() and __wakeup() methods to package the data into the shortest possible form. You can get better and faster results when you write your own __sleep() and __wakup() to implode() or pack() your data, than by using zlib compress() on the serialized object. ---- Manual Page -- http://www.php.net/manual/en/function.setcookie.php Edit -- http://master.php.net/manage/user-notes.php?action=edit+52648 Delete: added to the manual -- http://master.php.net/manage/user-notes.php?action=delete+52648&report=yes&reason=added+to+the+manual Delete: bad code -- http://master.php.net/manage/user-notes.php?action=delete+52648&report=yes&reason=bad+code Delete: spam -- http://master.php.net/manage/user-notes.php?action=delete+52648&report=yes&reason=spam Delete: useless -- http://master.php.net/manage/user-notes.php?action=delete+52648&report=yes&reason=useless Delete: other reasons -- http://master.php.net/manage/user-notes.php?action=delete+52648&report=yes Reject -- http://master.php.net/manage/user-notes.php?action=reject+52648&report=yes Search -- http://master.php.net/manage/user-notes.php