Mailinglisten-Archive |
>probiert hab ich schon diese varianten
>setcookie("daten",$daten, time()+7200, "/", "domain.de");
>setcookie("daten",$daten, time()+7200, "/", ".domain.de");
>setcookie("daten",$daten, time()+7200, "/", "www.domain.de");
>setcookie("daten",$daten, time()+7200, "/", "http://www.domain.de");
Hi Ralf,
domain=DOMAIN_NAME
When searching the cookie list for valid cookies, a comparison of the
domain attributes of the cookie is made with the Internet domain name of
the host from which the URL will be fetched. If there is a tail match, then
the cookie will go through path matching to see if it should be sent. "Tail
matching" means that domain attribute is matched against the tail of the
fully qualified domain name of the host. A domain attribute of "acme.com"
would match host names "anvil.acme.com" as well as
"shipping.crate.acme.com".
Only hosts within the specified domain can set a cookie for a domain and
domains must have at least two (2) or three (3) periods in them to prevent
domains of the form: ".com", ".edu", and "va.us". Any domain that fails
within one of the seven special top level domains listed below only require
two periods. Any other domain requires at least three. The seven special
top level domains are: "COM", "EDU", "NET", "ORG", "GOV", "MIL", and "INT".
The default value of domain is the host name of the server which generated
the cookie response.
http://wp.netscape.com/newsref/std/cookie_spec.html
MFG Wolfgang
php::bar PHP Wiki - Listenarchive