|Commit has since been removed from the repository and is no longer available.|
as a common function. Also deprecated CI_Input::set_cookie() which is now an alias for this new function. The new function will now replace cookies with the same name that were already set (either by set_cookie() or the native setcookie() and header() functions) in the PHP's headers queue. This fixes issue #1345 and supersedes PR #1780, which were aimed at fixing the Session library's behavior where it sent multiple cookies with the sess_cookie_name when the session cookie value had changed. It will now also always send the relatively new Max-Age cookie attribute (see http://tools.ietf.org/rfc/rfc6265.txt) and Expire will always be sent as a GMT timestamp, in an attempt to fix reported issues with Google Chrome (see issues #1726 and #1908). Cookies with the Secure attribute that are intended to only be send by the browser via encrypted connections will no longer be send if the website is not accessed via HTTPS. Also, the optional parameters' default values are changed to NULL instead of actually usable values, so that config_item() calls are only used if we're sure that the user/developer didn't set those intentionally. All usage of the native setcookie() function in CI has been replaces with set_cookie().