[html5] r5183 - [giow] (1) Define how WebSocket serialises Cookie headers as fields.

[whatwg at whatwg.org]

Author: ianh
Date: 2010-07-22 12:01:23 -0700 (Thu, 22 Jul 2010)
New Revision: 5183

Modified:
   complete.html
   source
Log:
[giow] (1) Define how WebSocket serialises Cookie headers as fields.

Modified: complete.html
===================================================================
--- complete.html	2010-07-22 08:13:49 UTC (rev 5182)
+++ complete.html	2010-07-22 19:01:23 UTC (rev 5183)
@@ -73046,6 +73046,15 @@
     considered a non-HTTP API for the purpose of cookie
     processing.</p>
 
+    <p>When one or more HTTP headers are to be added to <var title="">fields</var> for this step, each header must be added
+    separately, and each header must be added as one entry consisting
+    of the header's name in its canonical case, followed by a U+003A
+    COLON character (:) and a U+0020 SPACE character, followed by the
+    value with no use of continuation lines (i.e. containing no U+000A
+    LINE FEED characters).</p>
+
+    <!-- (Cookie headers only use one header for multiple cookies.) -->
+
 <!--(v2-ws-auth)
     <div class="example">
 

Modified: source
===================================================================
--- source	2010-07-22 08:13:49 UTC (rev 5182)
+++ source	2010-07-22 19:01:23 UTC (rev 5183)
@@ -82201,6 +82201,16 @@
     considered a non-HTTP API for the purpose of cookie
     processing.</p>
 
+    <p>When one or more HTTP headers are to be added to <var
+    title="">fields</var> for this step, each header must be added
+    separately, and each header must be added as one entry consisting
+    of the header's name in its canonical case, followed by a U+003A
+    COLON character (:) and a U+0020 SPACE character, followed by the
+    value with no use of continuation lines (i.e. containing no U+000A
+    LINE FEED characters).</p>
+
+    <!-- (Cookie headers only use one header for multiple cookies.) -->
+
 <!--(v2-ws-auth)
     <div class="example">