Ignore:
Timestamp:
Feb 17, 2010, 5:53:37 AM (10 years ago)
Author:
julian.reschke@…
Message:

lang/grammar

File:
1 edited

Legend:

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

    r756 r761  
    13131313     &MUST-NOT; be used unless the sender knows that the recipient can parse
    13141314     it; the presence in a request of a Range header with multiple byte-range
    1315      specifiers from a 1.1 client implies that the client can parse
     1315     specifiers from a HTTP/1.1 client implies that the client can parse
    13161316     multipart/byteranges responses.
    13171317    <list style="empty"><t>
    1318        A range header might be forwarded by a 1.0 proxy that does not
     1318       A range header might be forwarded by a HTTP/1.0 proxy that does not
    13191319       understand multipart/byteranges; in this case the server &MUST;
    13201320       delimit the message using methods defined in items 1, 3 or 5 of
     
    21162116   established to fetch each URL, increasing the load on HTTP servers
    21172117   and causing congestion on the Internet. The use of inline images and
    2118    other associated data often require a client to make multiple
     2118   other associated data often requires a client to make multiple
    21192119   requests of the same server in a short amount of time. Analysis of
    21202120   these performance problems and results from a prototype
     
    21852185   chooses to close the connection immediately after sending the
    21862186   response, it &SHOULD; send a Connection header including the
    2187    connection-token close.
     2187   connection-token "close".
    21882188</t>
    21892189<t>
     
    31013101</t>
    31023102<t>
    3103    Multiple Via field values represents each proxy or gateway that has
     3103   Multiple Via field values represent each proxy or gateway that has
    31043104   forwarded the message. Each recipient &MUST; append its information
    31053105   such that the end result is ordered according to the sequence of
     
    35713571   contains highly sensitive personal information, and/or information
    35723572   about organizations. Log information should be carefully guarded, and
    3573    appropriate guidelines for use developed and followed. (<xref target="abuse.of.server.log.information"/>).
     3573   appropriate guidelines for use should be developed and followed.
     3574   (<xref target="abuse.of.server.log.information"/>).
    35743575</t>
    35753576<t>
     
    35803581</t>
    35813582<t>
    3582    Users of a proxy need to be aware that they are no trustworthier than
    3583    the people who run the proxy; HTTP itself cannot solve this problem.
     3583   Users of a proxy need to be aware that proxies are no trustworthier than
     3584   the people who run them; HTTP itself cannot solve this problem.
    35843585</t>
    35853586<t>
     
    44354436<t>
    44364437   Clients &SHOULD; be tolerant in parsing the Status-Line and servers
    4437    tolerant when parsing the Request-Line. In particular, they &SHOULD;
    4438    accept any amount of WSP characters between fields, even though
     4438   &SHOULD; be tolerant when parsing the Request-Line. In particular, they
     4439   &SHOULD; accept any amount of WSP characters between fields, even though
    44394440   only a single SP is required.
    44404441</t>
     
    45794580   experimental implementations of persistent connections are faulty,
    45804581   and the new facilities in HTTP/1.1 are designed to rectify these
    4581    problems. The problem was that some existing 1.0 clients may be
     4582   problems. The problem was that some existing HTTP/1.0 clients may be
    45824583   sending Keep-Alive to a proxy server that doesn't understand
    45834584   Connection, which would then erroneously forward it to the next
     
    46614662</t>
    46624663<t>
    4663   Remove reference to non-existant identity transfer-coding value tokens.
     4664  Remove reference to non-existent identity transfer-coding value tokens.
    46644665  (Sections <xref format="counter" target="transfer.codings"/> and
    46654666  <xref format="counter" target="message.length"/>)
Note: See TracChangeset for help on using the changeset viewer.