$name
[,
string $value
[,
int $expire
= 0 [,
string $path
[,
string $domain
[,
bool $secure
= false [,
bool $httponly
= false ]]]]]] )
-
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
expire
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 '/foo/', the cookie will only be available within the /foo/ directory and all sub-directories such as /foo/bar/ ofdomain
. The default value is the current directory that the cookie is being set in. -
The domain that the cookie is available to. Setting the domain to 'www.example.com' will make the cookie available in the www subdomain and higher subdomains. Cookies available to a lower domain, such as 'example.com' will be available to higher subdomains, such as 'www.example.com'. 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"] ).
name
value
expire
path
domain
secure
(译:当前的cookie只能接受来自客户端的https请求,当这个参数设置为true时,cookie只会在安全连接存在时生成,在服务端,程序员只有在这种连接状态时才能设置这个参数)
-
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
orFALSE
httponly
例
a.php
<?php
$s = setcookie('helloworld','good',$time,'/','xxx.com',true);
$s = setcookie('helloworld2','gooFFDDDd',$time,'/','xxx.com');
$s = setcookie('helloworld3','helloworld3gooFFDDDd',$time,'/','xxx.com',false,true);
$s = setcookie('helloworld4','helloworld3gooFFDDDd',$time,'/','xxx.com',false,false);
b.html
<script type="text/javascript">
function getCookie(c_name){
if (document.cookie.length>0){
//先查询cookie是否为空,为空就
return ""
c_start=document.cookie.indexOf(c_name + "=")
//通过String对象的indexOf()来检查这个cookie是否存在,不存在就为 -1
if (c_start!=-1){
c_start=c_start + c_name.length+1
c_end=document.cookie.indexOf(";",c_start)
if (c_end==-1) c_end=document.cookie.length
return unescape(document.cookie.substring(c_start,c_end))
}
}
return ""
}
var cookhttpsval=getCookie('helloworld');
alert(cookhttpsval); //不显示
var cookval=getCookie('helloworld2');
alert(cookval); //显示
var cookval3=getCookie('helloworld3');
alert(cookval3); //不显示
var cookval4=getCookie('helloworld4');
alert(cookval4);//显示
</script>