Jesus · Bible · HTML · CSS · JS · PHP · SVG · Applications



The setrawcookie of Network for PHP send a cookie without urlencoding the cookie value.


setrawcookie ( string $name [, string $value [, int $expires = 0 [, string $path [, string $domain [, bool $secure = FALSE [, bool $httponly = FALSE ]]]]]] ) : bool
setrawcookie ( string $name [, string $value [, array $options = [] ]] ) : bool



The name of the cookie.


The value of the cookie. This value is stored on the clients computer; do not store sensitive information. Assuming the name is 'cookiename', this value is retrieved through $_COOKIE['cookiename']


The time the cookie expires. This is a Unix timestamp so is in number of seconds since the epoch. In other words, you'll most likely set this with the time() function plus the number of seconds before you want it to expire. Or you might use mktime(). time()+60*60*24*30 will set the cookie to expire in 30 days. If set to 0, or omitted, the cookie will expire at the end of the session (when the browser closes). Note: You may notice the expires parameter takes on a Unix timestamp, as opposed to the date format Wdy, DD-Mon-YYYY HH:MM:SS GMT, this is because PHP does this conversion internally.


The path on the server in which the cookie will be available on. If set to '/', the cookie will be available within the entire domain. If set to '/test/', the cookie will only be available within the /test/ directory and all sub-directories such as /test/stuff/ of domain. The default value is the current directory that the cookie is being set in.


The (sub)domain that the cookie is available to. Setting this to a subdomain (such as '') will make the cookie available to that subdomain and all other sub-domains of it (i.e. To make the cookie available to the whole domain (including all subdomains of it), simply set the value to the domain name ('', in this case). Older browsers still implementing the deprecated » RFC 2109 may require a leading . to match all subdomains.


Indicates that the cookie should only be transmitted over a secure HTTPS connection from the client. When set to TRUE, the cookie will only be set if a secure connection exists. On the server-side, it's on the programmer to send this kind of cookie only on secure connection (e.g. with respect to $_SERVER["HTTPS"]).


When TRUE the cookie will be made accessible only through the HTTP protocol. This means that the cookie won't be accessible by scripting languages, such as JavaScript. It has been suggested that this setting can effectively help to reduce identity theft through XSS attacks (although it is not supported by all browsers), but that claim is often disputed. Added in PHP 5.2.0. TRUE or FALSE


An associative array which may have any of the keys expires, path, domain, secure, httponly and samesite. If any other key is present an error of level E_WARNING is generated. The values have the same meaning as described for the parameters with the same name. The value of the samesite element should be either None, Lax or Strict. If any of the allowed options are not given, their default values are the same as the default values of the explicit parameters. If the samesite element is omitted, no SameSite cookie attribute is set.


Returns TRUE on success or FALSE on failure.




$value = 'something from somewhere';

setrawcookie("TestCookie", $value);
setrawcookie("TestCookie", $value, time()+3600);  /* expire in 1 hour */
setrawcookie("TestCookie", $value, time()+3600, "/~path/", "", 1);