"Kim Jensen" <kj@jmt.dk> wrote in <96iska$7hu$1@news.inet.tele.dk>:
>> >Hvis ikke de angiver denne property, sættes den automatisk til det
>domain,
>> >hvorfra cookien blev dannet.
>> fx kan det bruges til at sikre, at en cookie kun kan læses af siderne på
>>
www.geocities.com/~user1 ... og ikke af siderne på
>
www.geocities.com/~user2
>
>Well, det kræver vel nærmere brug af .path property'en!?
>
Jeg kiggede lige dokumentationen igennem igen for at se, om jeg havde læst
indenad.
På MSDN står der:
Specifying the domain name, using the pattern domain=<domain_name>, is
optional for persistent cookies and is used to indicate the end of the
domain for which the cookie is valid. Session cookies that specify a domain
are rejected. If the specified domain name ending matches the request, the
cookie tries to match the path to determine if the cookie should be sent.
For example, if the domain name ending is .microsoft.com, requests to
home.microsoft.com and support.microsoft.com would be checked to see if the
specified pattern matches the request. The domain name must have at least
two or three periods in it to prevent cookies from being set for widely used
domain name endings, such as .com, .edu, and co.jp. Allowable domain names
would be similar to .microsoft.com, .someschool.edu, and .someserver.co.jp.
Only hosts within the specified domain can set a cookie for a domain
Som jeg nu læser det, er det for at kunne specificere subdomæner - og ikke
underfoldere.
Jesper
http://msdn.microsoft.com/workshop/networking/wininet/overview/http_cookies.
asp
--
Why don't we go see a play tonight ?
- wife of Abraham Lincoln