Skip to content
Permalink
Browse files
[e] (0) sync with http-state
git-svn-id: http://svn.whatwg.org/webapps@5214 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
Hixie committed Jul 28, 2010
1 parent 6027906 commit c38a20b515497e3b58859d4b4c9e186f05c679aa
Showing 3 changed files with 18 additions and 6 deletions.
@@ -8082,7 +8082,9 @@ <h4 id=resource-metadata-management><span class=secno>3.1.3 </span><dfn>Resource
<code><a href=#security_err>SECURITY_ERR</a></code> exception. Otherwise, the user agent must
first <a href=#obtain-the-storage-mutex>obtain the storage mutex</a> and then return the
cookie-string for <a href="#the-document's-address">the document's address</a> for a
"non-HTTP" API. <a href=#refsCOOKIES>[COOKIES]</a></p>
"non-HTTP" API, decoded as UTF-8, with bytes or sequences of bytes
that are not valid UTF-8 sequences interpreted as U+FFFD REPLACEMENT
CHARACTERs. <a href=#refsCOOKIES>[COOKIES]</a> <a href=#refsRFC3629>[RFC3629]</a></p>

<p>On setting, if the document is a <a href=#cookie-free-document-object>cookie-free
<code>Document</code> object</a>, then the user agent must do
@@ -8093,7 +8095,7 @@ <h4 id=resource-metadata-management><span class=secno>3.1.3 </span><dfn>Resource
as it would when <span title="receives a
set-cookie-string">receiving a set-cookie-string</span> for
<a href="#the-document's-address">the document's address</a> via a "non-HTTP" API, consisting
of the new value. <a href=#refsCOOKIES>[COOKIES]</a></p>
of the new value encoded as UTF-8. <a href=#refsCOOKIES>[COOKIES]</a> <a href=#refsRFC3629>[RFC3629]</a></p>

<p class=note>Since the <code title=dom-document-cookie><a href=#dom-document-cookie>cookie</a></code> attribute is accessible
across frames, the path restrictions on cookies are only a tool to
10 index
@@ -8006,7 +8006,9 @@ interface <dfn id=htmldocument>HTMLDocument</dfn> {
<code><a href=#security_err>SECURITY_ERR</a></code> exception. Otherwise, the user agent must
first <a href=#obtain-the-storage-mutex>obtain the storage mutex</a> and then return the
cookie-string for <a href="#the-document's-address">the document's address</a> for a
"non-HTTP" API. <a href=#refsCOOKIES>[COOKIES]</a></p>
"non-HTTP" API, decoded as UTF-8, with bytes or sequences of bytes
that are not valid UTF-8 sequences interpreted as U+FFFD REPLACEMENT
CHARACTERs. <a href=#refsCOOKIES>[COOKIES]</a> <a href=#refsRFC3629>[RFC3629]</a></p>

<p>On setting, if the document is a <a href=#cookie-free-document-object>cookie-free
<code>Document</code> object</a>, then the user agent must do
@@ -8017,7 +8019,7 @@ interface <dfn id=htmldocument>HTMLDocument</dfn> {
as it would when <span title="receives a
set-cookie-string">receiving a set-cookie-string</span> for
<a href="#the-document's-address">the document's address</a> via a "non-HTTP" API, consisting
of the new value. <a href=#refsCOOKIES>[COOKIES]</a></p>
of the new value encoded as UTF-8. <a href=#refsCOOKIES>[COOKIES]</a> <a href=#refsRFC3629>[RFC3629]</a></p>

<p class=note>Since the <code title=dom-document-cookie><a href=#dom-document-cookie>cookie</a></code> attribute is accessible
across frames, the path restrictions on cookies are only a tool to
@@ -87512,6 +87514,10 @@ interface <a href=#htmldocument>HTMLDocument</a> {
<dd><cite><a href=http://www.ietf.org/rfc/rfc3548.txt>The Base16, Base32,
and Base64 Data Encodings</a></cite>, S. Josefsson. IETF.</dd>

<dt id=refsRFC3629>[RFC3629]</dt>
<dd><cite><a href=http://www.ietf.org/rfc/rfc3629.txt>UTF-8, a
transformation format of ISO 10646</a></cite>, F. Yergeau. IETF.</dd>

<dt id=refsRFC3864>[RFC3864]</dt>
<dd><cite><a href=http://www.ietf.org/rfc/rfc3864.txt>Registration Procedures
for Message Header Fields</a></cite>, G. Klyne, M. Nottingham,
8 source
@@ -7926,7 +7926,10 @@ interface <dfn>HTMLDocument</dfn> {
<code>SECURITY_ERR</code> exception. Otherwise, the user agent must
first <span>obtain the storage mutex</span> and then return the
cookie-string for <span>the document's address</span> for a
"non-HTTP" API. <a href="#refsCOOKIES">[COOKIES]</a></p>
"non-HTTP" API, decoded as UTF-8, with bytes or sequences of bytes
that are not valid UTF-8 sequences interpreted as U+FFFD REPLACEMENT
CHARACTERs. <a href="#refsCOOKIES">[COOKIES]</a> <a
href="#refsRFC3629">[RFC3629]</a></p>

<p>On setting, if the document is a <span>cookie-free
<code>Document</code> object</span>, then the user agent must do
@@ -7937,7 +7940,8 @@ interface <dfn>HTMLDocument</dfn> {
as it would when <span title="receives a
set-cookie-string">receiving a set-cookie-string</span> for
<span>the document's address</span> via a "non-HTTP" API, consisting
of the new value. <a href="#refsCOOKIES">[COOKIES]</a></p>
of the new value encoded as UTF-8. <a
href="#refsCOOKIES">[COOKIES]</a> <a href="#refsRFC3629">[RFC3629]</a></p>

<p class="note">Since the <code
title="dom-document-cookie">cookie</code> attribute is accessible

0 comments on commit c38a20b

Please sign in to comment.