* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Ticket #359: 359.diff

File 359.diff, 4.3 KB (added by julian.reschke@gmx.de, 2 years ago)

Proposed patch for Part 1

  • p1-messaging.xml

     
    26772677  <iref primary="true" item="Connection header field" x:for-anchor=""/> 
    26782678  <iref primary="true" item="Header Fields" subitem="Connection" x:for-anchor=""/> 
    26792679  <x:anchor-alias value="Connection"/> 
    2680   <x:anchor-alias value="connection-token"/> 
     2680  <x:anchor-alias value="connection-option"/> 
    26812681<t> 
    26822682   The "Connection" header field allows the sender to specify 
    26832683   options that are desired only for that particular connection. 
     
    26942694<t> 
    26952695   The Connection header field's value has the following grammar: 
    26962696</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> 
    27002700</artwork></figure> 
    27012701<t> 
     2702   Connection options are compared case-insensitively. 
     2703</t> 
     2704<t> 
    27022705   A proxy or gateway &MUST; parse a received Connection 
    27032706   header field before a message is forwarded and, for each 
    2704    connection-token in this field, remove any header field(s) from 
    2705    the message with the same name as the connection-token, and then 
     2707   connection-option in this field, remove any header field(s) from 
     2708   the message with the same name as the connection-option, and then 
    27062709   remove the Connection header field itself or replace it with the 
    27072710   sender's own connection options for the forwarded message. 
    27082711</t> 
     
    27182721   might not be needed if there are no parameters associated with that 
    27192722   connection option.  Recipients that trigger certain connection 
    27202723   behavior based on the presence of connection options &MUST; do so 
    2721    based on the presence of the connection-token rather than only the 
     2724   based on the presence of the connection-option rather than only the 
    27222725   presence of the optional header field.  In other words, if the 
    27232726   connection option is received as a header field but not indicated 
    27242727   within the Connection field-value, then the recipient &MUST; ignore 
     
    27282731<t> 
    27292732   When defining new connection options, specifications ought to 
    27302733   carefully consider existing deployed header fields and ensure 
    2731    that the new connection-token does not share the same name as 
     2734   that the new connection option does not share the same name as 
    27322735   an unrelated header field that might already be deployed. 
    2733    Defining a new connection-token essentially reserves that potential 
     2736   Defining a new connection option essentially reserves that potential 
    27342737   field-name for carrying additional information related to the 
    27352738   connection option, since it would be unwise for senders to use 
    27362739   that field-name for anything else. 
     
    49014904<artwork type="abnf" name="p1-messaging.parsed-abnf"> 
    49024905<x:ref>BWS</x:ref> = OWS 
    49034906 
    4904 <x:ref>Connection</x:ref> = *( "," OWS ) connection-token *( OWS "," [ OWS 
    4905  connection-token ] ) 
     4907<x:ref>Connection</x:ref> = *( "," OWS ) connection-option *( OWS "," [ OWS 
     4908 connection-option ] ) 
    49064909<x:ref>Content-Length</x:ref> = 1*DIGIT 
    49074910 
    49084911<x:ref>HTTP-message</x:ref> = start-line *( header-field CRLF ) CRLF [ message-body 
     
    49424945<x:ref>chunk-size</x:ref> = 1*HEXDIG 
    49434946<x:ref>chunked-body</x:ref> = *chunk last-chunk trailer-part CRLF 
    49444947<x:ref>comment</x:ref> = "(" *( ctext / quoted-cpair / comment ) ")" 
    4945 <x:ref>connection-token</x:ref> = token 
     4948connection-option = token 
    49464949<x:ref>ctext</x:ref> = OWS / %x21-27 ; '!'-''' 
    49474950 / %x2A-5B ; '*'-'[' 
    49484951 / %x5D-7E ; ']'-'~' 
     
    58235826      "make IANA policy definitions consistent" 
    58245827    </t> 
    58255828    <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> 
    58265833      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/361"/>: 
    58275834      "ABNF requirements for recipients" 
    58285835    </t>