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

Timestamp:

Jul 3, 2012, 12:48:00 AM (7 years ago)

Author:

julian.reschke@…

Message:

Avoid use of "connection-token" outside the header field definition; use "connection option" instead; consistently quote the "close" connection option.

File:

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

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

@@ -2926 +2926 @@
    An HTTP/1.1 server &MAY; assume that a HTTP/1.1 client intends to
    maintain a persistent connection unless a Connection header field including
-   the connection-token "close" was sent in the request. If the server
+   the connection option "close" was sent in the request. If the server
    chooses to close the connection immediately after sending the
    response, it &SHOULD; send a Connection header field including the
-   connection-token "close".
+   connection option "close".
 </t>
 <t>
    An HTTP/1.1 client &MAY; expect a connection to remain open, but would
    decide to keep it open based on whether the response from a server
-   contains a Connection header field with the connection-token close. In case
+   contains a Connection header field with the connection option "close". In case
    the client does not want to maintain a connection for more than that
    request, it &SHOULD; send a Connection header field including the
-   connection-token close.
-</t>
-<t>
-   If either the client or the server sends the close token in the
+   connection option "close".
+</t>
+<t>
+   If either the client or the server sends the "close" option in the
    Connection header field, that request becomes the last one for the
    connection.
@@ -4885 +4885 @@
 </t>
 <t>
-  Clarify exactly when close connection options have to be sent.
+  Clarify exactly when "close" connection options have to be sent.
   (<xref target="header.connection"/>)
 </t>