[e] (0) Clarify that WebSocket is not importing all possible cookie-r…

…elated specifications; UAs can pick which cookie specs, if any, they support. Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=9149 git-svn-id: http://svn.whatwg.org/webapps@4894 340c8d12-0b0e-0410-8428-c7bf67bfef74
whatwg · Mar 29, 2010 · 05a344a · 05a344a
1 parent c2a4cf7
commit 05a344a
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 2 deletions.
diff --git a/complete.html b/complete.html
@@ -69594,7 +69594,8 @@ <h6 id=opening-handshake-0><span class=secno>10.3.4.3.1 </span>Opening handshake
      <dt>If the entry's name is "<code title=http-setcookie>set-cookie</code>" or "<code title=http-setcookie2>set-cookie2</code>" or another
      cookie-related field name</dt>
 
-     <dd><p>Handle the cookie as defined by the appropriate
+     <dd><p>If the relevant specification is supported by the user
+     agent, handle the cookie as defined by the appropriate
      specification, with the resource being the one with the host <var title="">host</var>, the port <var title="">port</var>, the path
      (and possibly query parameters) <var title="">resource
      name</var>, and the scheme <code title="">http</code> if <var title="">secure</var> is false and <code title="">https</code> if

diff --git a/source b/source
@@ -78104,7 +78104,8 @@ Proxy-authorization: Basic ZWRuYW1vZGU6bm9jYXBlcyE=</pre>
      title="http-setcookie2">set-cookie2</code>" or another
      cookie-related field name</dt>
 
-     <dd><p>Handle the cookie as defined by the appropriate
+     <dd><p>If the relevant specification is supported by the user
+     agent, handle the cookie as defined by the appropriate
      specification, with the resource being the one with the host <var
      title="">host</var>, the port <var title="">port</var>, the path
      (and possibly query parameters) <var title="">resource