Ignore:
Timestamp:
Jul 21, 2010, 7:16:15 AM (9 years ago)
Author:
julian.reschke@…
Message:

Remove paragraphs in "changes from 2068" about message length handling that do not apply anymore after recent changes; update the remaining to not point to the other parts (see #90)(see #95)(see #109)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p3-payload.xml

    r858 r859  
    27452745<section title="Changes from RFC 2068" anchor="changes.from.rfc.2068">
    27462746<t>
    2747    Transfer-coding and message lengths all interact in ways that
    2748    required fixing exactly when chunked encoding is used (to allow for
    2749    transfer encoding that may not be self delimiting); it was important
    2750    to straighten out exactly how message lengths are computed.
    2751 </t>
    2752 <t>
    27532747   Charset wildcarding is introduced to avoid explosion of character set
    27542748   names in accept headers. (<xref target="header.accept-charset"/>)
Note: See TracChangeset for help on using the changeset viewer.