Ticket #184: 184.2.diff

File 184.2.diff, 1.7 KB (added by julian.reschke@…, 12 years ago)

Proposed patch for part 1.

  • p1-messaging.xml

     
    43704370   It is beyond the scope of a protocol specification to mandate
    43714371   compliance with previous versions. HTTP/1.1 was deliberately
    43724372   designed, however, to make supporting previous versions easy. It is
    4373    worth noting that, at the time of composing this specification
    4374    (1996), we would expect commercial HTTP/1.1 servers to:
     4373   worth noting that, at the time of composing this specification, we would
     4374   expect general-purpose HTTP/1.1 servers to:
    43754375  <list style="symbols">
    4376      <t>recognize the format of the Request-Line for HTTP/0.9, 1.0, and
    4377         1.1 requests;</t>
    4378 
    4379      <t>understand any valid request in the format of HTTP/0.9, 1.0, or
     4376     <t>understand any valid request in the format of HTTP/1.0 and
    43804377        1.1;</t>
    43814378
    43824379     <t>respond appropriately with a message in the same major version
     
    43864383<t>
    43874384   And we would expect HTTP/1.1 clients to:
    43884385  <list style="symbols">
    4389      <t>recognize the format of the Status-Line for HTTP/1.0 and 1.1
    4390         responses;</t>
    4391 
    4392      <t>understand any valid response in the format of HTTP/0.9, 1.0, or
     4386     <t>understand any valid response in the format of HTTP/1.0 or
    43934387        1.1.</t>
    43944388  </list>
    43954389</t>
     
    51665160      "IP addresses in URLs"
    51675161    </t>
    51685162    <t>
     5163      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/184"/>:
     5164      "HTTP/0.9 support"
     5165    </t>
     5166    <t>
    51695167      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/188"/>:
    51705168      "pick IANA policy (RFC5226) for Transfer Coding / Content Coding"
    51715169    </t>