Ignore:
Timestamp:
Jan 4, 2013, 11:12:36 PM (7 years ago)
Author:
fielding@…
Message:

Requirements are not allowed in appendices. They have been changed to prose.
Changes from RFC2616 have been rewritten for consistency and to remove changes
that are only editorial. Addresses #419

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r2081 r2083  
    143143<t>
    144144   The Hypertext Transfer Protocol (HTTP) is an application-level
    145    request/response protocol that uses extensible semantics and MIME-like
     145   request/response protocol that uses extensible semantics and self-descriptive
    146146   message payloads for flexible interaction with network-based hypertext
    147147   information systems. This document is the first in a series of documents
     
    46764676<t>
    46774677   HTTP/1.1 introduces the <x:ref>Transfer-Encoding</x:ref> header field
    4678    (<xref target="header.transfer-encoding"/>). Proxies/gateways &MUST; remove
    4679    any transfer coding prior to forwarding a message via a MIME-compliant
    4680    protocol.
     4678   (<xref target="header.transfer-encoding"/>).
     4679   Transfer codings need to be decoded prior to forwarding an HTTP message
     4680   over a MIME-compliant protocol.
    46814681</t>
    46824682</section>
Note: See TracChangeset for help on using the changeset viewer.