Changeset 1706 for draft-ietf-httpbis/latest/p1-messaging.xml

Timestamp:

03/07/12 09:29:18 (10 years ago)

Author:

julian.reschke@…

Message:

clarify connection header field values are case-insensitive (see #359)

File:

• draft-ietf-httpbis/latest/p1-messaging.xml (modified) (7 diffs)

draft-ietf-httpbis/latest/p1-messaging.xml

@@ -2678 +2678 @@
   <iref primary="true" item="Header Fields" subitem="Connection" x:for-anchor=""/>
   <x:anchor-alias value="Connection"/>
-  <x:anchor-alias value="connection-token"/>
+  <x:anchor-alias value="connection-option"/>
 <t>
    The "Connection" header field allows the sender to specify
@@ -2695 +2695 @@
    The Connection header field's value has the following grammar:
 </t>
-<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Connection"/><iref primary="true" item="Grammar" subitem="connection-token"/>
-  <x:ref>Connection</x:ref>       = 1#<x:ref>connection-token</x:ref>
-  <x:ref>connection-token</x:ref> = <x:ref>token</x:ref>
+<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Connection"/><iref primary="true" item="Grammar" subitem="connection-option"/>
+  <x:ref>Connection</x:ref>        = 1#<x:ref>connection-option</x:ref>
+  <x:ref>connection-option</x:ref> = <x:ref>token</x:ref>
 </artwork></figure>
+<t>
+   Connection options are compared case-insensitively.
+</t>
 <t>
    A proxy or gateway &MUST; parse a received Connection
    header field before a message is forwarded and, for each
-   connection-token in this field, remove any header field(s) from
-   the message with the same name as the connection-token, and then
+   connection-option in this field, remove any header field(s) from
+   the message with the same name as the connection-option, and then
    remove the Connection header field itself or replace it with the
    sender's own connection options for the forwarded message.
@@ -2719 +2722 @@
    connection option.  Recipients that trigger certain connection
    behavior based on the presence of connection options &MUST; do so
-   based on the presence of the connection-token rather than only the
+   based on the presence of the connection-option rather than only the
    presence of the optional header field.  In other words, if the
    connection option is received as a header field but not indicated
@@ -2729 +2732 @@
    When defining new connection options, specifications ought to
    carefully consider existing deployed header fields and ensure
-   that the new connection-token does not share the same name as
+   that the new connection option does not share the same name as
    an unrelated header field that might already be deployed.
-   Defining a new connection-token essentially reserves that potential
+   Defining a new connection option essentially reserves that potential
    field-name for carrying additional information related to the
    connection option, since it would be unwise for senders to use
@@ -4902 +4905 @@
 <x:ref>BWS</x:ref> = OWS
 
-<x:ref>Connection</x:ref> = *( "," OWS ) connection-token *( OWS "," [ OWS
- connection-token ] )
+<x:ref>Connection</x:ref> = *( "," OWS ) connection-option *( OWS "," [ OWS
+ connection-option ] )
 <x:ref>Content-Length</x:ref> = 1*DIGIT
 
@@ -4943 +4946 @@
 <x:ref>chunked-body</x:ref> = *chunk last-chunk trailer-part CRLF
 <x:ref>comment</x:ref> = "(" *( ctext / quoted-cpair / comment ) ")"
-<x:ref>connection-token</x:ref> = token
+<x:ref>connection-option</x:ref> = token
 <x:ref>ctext</x:ref> = OWS / %x21-27 ; '!'-'''
  / %x2A-5B ; '*'-'['
@@ -5824 +5827 @@
     </t>
     <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/359"/>:
+      "clarify connection header field values are case-insensitive"
+    </t>
+    <t>
       <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/361"/>:
       "ABNF requirements for recipients"