note 73819 added to function.setcookie

It would seem that set_cookie will still set a cookie via HTTP, even if the secure parameter is true. So even if your site uses HTTPS/SSL to communicate sensitive data, if the initial cookie was set by set_cookie via HTTP, an attacker listening on the wire could easily spoof a visitor's cookie and gain access to their session. See: http://bugs.php.net/bug.php?id=40778 ---- Server IP: 216.194.113.175 Probable Submitter: 69.238.96.156 ---- Manual Page -- http://www.php.net/manual/en/function.setcookie.php Edit -- https://master.php.net/note/edit/73819 Del: integrated -- https://master.php.net/note/delete/73819/integrated Del: useless -- https://master.php.net/note/delete/73819/useless Del: bad code -- https://master.php.net/note/delete/73819/bad+code Del: spam -- https://master.php.net/note/delete/73819/spam Del: non-english -- https://master.php.net/note/delete/73819/non-english Del: in docs -- https://master.php.net/note/delete/73819/in+docs Del: other reasons-- https://master.php.net/note/delete/73819 Reject -- https://master.php.net/note/reject/73819 Search -- https://master.php.net/manage/user-notes.php