Changeset 1706 for draft-ietf-httpbis/latest/p1-messaging.xml
- Timestamp:
- 03/07/12 09:29:18 (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.xml
r1705 r1706 2678 2678 <iref primary="true" item="Header Fields" subitem="Connection" x:for-anchor=""/> 2679 2679 <x:anchor-alias value="Connection"/> 2680 <x:anchor-alias value="connection- token"/>2680 <x:anchor-alias value="connection-option"/> 2681 2681 <t> 2682 2682 The "Connection" header field allows the sender to specify … … 2695 2695 The Connection header field's value has the following grammar: 2696 2696 </t> 2697 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Connection"/><iref primary="true" item="Grammar" subitem="connection- token"/>2698 <x:ref>Connection</x:ref> = 1#<x:ref>connection-token</x:ref>2699 <x:ref>connection- token</x:ref> = <x:ref>token</x:ref>2697 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Connection"/><iref primary="true" item="Grammar" subitem="connection-option"/> 2698 <x:ref>Connection</x:ref> = 1#<x:ref>connection-option</x:ref> 2699 <x:ref>connection-option</x:ref> = <x:ref>token</x:ref> 2700 2700 </artwork></figure> 2701 <t> 2702 Connection options are compared case-insensitively. 2703 </t> 2701 2704 <t> 2702 2705 A proxy or gateway &MUST; parse a received Connection 2703 2706 header field before a message is forwarded and, for each 2704 connection- token in this field, remove any header field(s) from2705 the message with the same name as the connection- token, and then2707 connection-option in this field, remove any header field(s) from 2708 the message with the same name as the connection-option, and then 2706 2709 remove the Connection header field itself or replace it with the 2707 2710 sender's own connection options for the forwarded message. … … 2719 2722 connection option. Recipients that trigger certain connection 2720 2723 behavior based on the presence of connection options &MUST; do so 2721 based on the presence of the connection- token rather than only the2724 based on the presence of the connection-option rather than only the 2722 2725 presence of the optional header field. In other words, if the 2723 2726 connection option is received as a header field but not indicated … … 2729 2732 When defining new connection options, specifications ought to 2730 2733 carefully consider existing deployed header fields and ensure 2731 that the new connection -token does not share the same name as2734 that the new connection option does not share the same name as 2732 2735 an unrelated header field that might already be deployed. 2733 Defining a new connection -token essentially reserves that potential2736 Defining a new connection option essentially reserves that potential 2734 2737 field-name for carrying additional information related to the 2735 2738 connection option, since it would be unwise for senders to use … … 4902 4905 <x:ref>BWS</x:ref> = OWS 4903 4906 4904 <x:ref>Connection</x:ref> = *( "," OWS ) connection- token *( OWS "," [ OWS4905 connection- token ] )4907 <x:ref>Connection</x:ref> = *( "," OWS ) connection-option *( OWS "," [ OWS 4908 connection-option ] ) 4906 4909 <x:ref>Content-Length</x:ref> = 1*DIGIT 4907 4910 … … 4943 4946 <x:ref>chunked-body</x:ref> = *chunk last-chunk trailer-part CRLF 4944 4947 <x:ref>comment</x:ref> = "(" *( ctext / quoted-cpair / comment ) ")" 4945 <x:ref>connection- token</x:ref> = token4948 <x:ref>connection-option</x:ref> = token 4946 4949 <x:ref>ctext</x:ref> = OWS / %x21-27 ; '!'-''' 4947 4950 / %x2A-5B ; '*'-'[' … … 5824 5827 </t> 5825 5828 <t> 5829 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/359"/>: 5830 "clarify connection header field values are case-insensitive" 5831 </t> 5832 <t> 5826 5833 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/361"/>: 5827 5834 "ABNF requirements for recipients"
Note: See TracChangeset
for help on using the changeset viewer.