Set-Cookie:
Set-Cookie: 欄の
Set-Cookie: NAME=VALUE; expires=DATE; path=PATH; domain=DOMAIN_NAME; secureのように名前と値の組 (
Set-Cookie: set-cookie-header = "Set-Cookie:"SP set-cookie-string set-cookie-string =cookie-pair *( ";"SP cookie-av )
Set-Cookie Set-Cookie2
#) でないSet-Cookie:
, Set-Cookie: , Expires ,
Set-Cookie Set-Cookie2 ; ; = = WSP ; ; ; = = WSP Set-Cookie:
Max-Age Expires Domain Path Secure HttpOnly
NAME が同じ
Path NAME
とありますが、 Domain /foo と /foo/bar で同じ名前の /foo/bar では両方が有効になります。
NAME が同じで
Path Domain NAME が同じで
Path Domain Port
Max-Age 0 Discard
Set-Cookie: Set-Cookie: Set-Cookie2: Cache-Control: <meta http-equiv=Set-Cookie>
Set-Cookie:
の構文は
--cookie
でも使われています。
Set-Cookie:
の構文は
cookies
でも使われています。
cookies
Set the cookies to be sent in future requests. The format of each cookie is the same as the value of a Set-Cookie HTTP response field. Multiple cookies can be delimited by a newline character.
HTTP::Cookie は、
Set-Cookie3 という名称を使っています。
Set-Cookie: 欄Cookie: Set-Cookie2: 欄
Set-Cookie: Set-Cookie2: Set-Cookie: Set-Cookie2: Cookie: Set-Cookie: Cookie: Cookie2:
- Cookie.serVersion(1)としたクッキーを送信した場合、 Set-CookieとSet-Cookie2ヘッダの両方がクライアントに送信されていました。
- NN4.7とIE5では、Set-Cookie2ヘッダはサポートしていないようです。
- [18:02] <abarth> annevk42: if you're interested in the cookie stuff, you should join the mailing list and comment on the charter
- [18:02] <abarth> annevk42: in general, i'm trying to keep the focus narrow
- [18:03] <abarth> annevk42: speccing cookie2 is going to take a lot more work and a lot more time than speccing cookie0
- [18:18] <annevk2> abarth, if you're going to spec cookies as implemented set-cookie2 is relevant, no?
- [18:18] <abarth> annevk2: depends how widely its used
- [18:18] <abarth> there was a recent message to the list
- [18:19] <abarth> that suggested very few sites use it
- [18:19] <abarth> i'm not sure we want to lock down the behavior of cookie2
- [18:19] <annevk2> hmm, if we could actually get impl to remove support for it that'd be cool
- [18:19] <abarth> which user agents implement it?
- [18:20] <annevk2> I thougt set-cookie2, not cookie2, was implemented, but maybe not
- [18:20] <abarth> i know they're in opera
- [18:20] <abarth> but i'm not sure where else
- [18:20] <annevk2> interesting
- [18:22] <annevk2> if we're the only ones by all means don't spec it or simply say it's obsolete
- [18:23] <annevk2> if we need extensions we can prolly extend cookie0 somehow once the processing model is written down
- [18:23] <abarth> i don't think we want to say it's obsolete. cookie suck in a number of ways. it would be good to have a long term plan for how to dig ourselves out of the mess
- [18:23] <abarth> yeah, that's a good point
- [18:23] <abarth> that's what 2109 originally tried to do with Version=1
- [18:24] <abarth> but i think they put the cart a bit in front of the horse
- [18:24] <annevk2> besides rough consensus you need running code :p
- [18:24] <annevk2> (also, versioning sucks :))
Set-Cookie Set-Cookie2 やCache-Control :no-cache ="set-cookie"
を指定するCache-Control :no-cache ="set-cookie2"
Cache-Control :private
Cache-Control :must-revalidate ,max-age =0
Cache-Control :proxy-revalidate ,max-age =0
Cache-Control :max-age =0
Expires: Cache-Control Set-Cookie Set-Cookie2
この
この
Apache2.2 と IE6 でsetcookie()で既存の同じ名前と値を設定する場合、有効期限(期間)は更新されない。 有効期限0で一旦セットしてから同じ有効期間をセットする。
setcookie($name, $name, 0); setcookie($name, $name, time()+60*60*24*365);
block-cookies
The engine strips all cookies from the header before sending the request to the server. Safari's own privacy policy takes precedence, so that only cookies that would otherwise be accepted by the privacy policy can be blocked.