Ignore:
Timestamp:
Nov 1, 2012, 11:46:15 AM (7 years ago)
Author:
julian.reschke@…
Message:

editorial improvements (ack Dan W.)

File:
1 edited

Legend:

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

    r1963 r1964  
    547547   can be understood in isolation.  Many implementations depend on HTTP's
    548548   stateless design in order to reuse proxied connections or dynamically
    549    load balance requests across multiple servers.  Hence, servers &MUST-NOT;
     549   load-balance requests across multiple servers.  Hence, servers &MUST-NOT;
    550550   assume that two requests on the same connection are from the same user
    551551   agent unless the connection is secured and specific to that agent.
     
    758758   the minor version was not incremented for the changes introduced between
    759759   <xref target="RFC2068"/> and <xref target="RFC2616"/>, and this revision
    760    is specifically avoiding any such changes to the protocol.
     760   has specifically avoiding any such changes to the protocol.
    761761</t>
    762762</section>
     
    29972997<t>
    29982998   A server that receives a <x:ref>close</x:ref> connection option &MUST;
    2999    initiate a lingering close of the connection after it sends the final
    3000    response to the request that contained <x:ref>close</x:ref>.
     2999   initiate a lingering close (see below) of the connection after it sends the
     3000   final response to the request that contained <x:ref>close</x:ref>.
    30013001   The server &SHOULD; include a <x:ref>close</x:ref> connection option
    30023002   in its final response on that connection. The server &MUST-NOT; process
     
    35933593   HTTP clients rely heavily on the Domain Name Service (DNS), and are thus
    35943594   generally prone to security attacks based on the deliberate misassociation
    3595    of IP addresses and DNS names not protected by DNSSec. Clients need to be
     3595   of IP addresses and DNS names not protected by DNSSEC. Clients need to be
    35963596   cautious in assuming the validity of an IP number/DNS name association unless
    3597    the response is protected by DNSSec (<xref target="RFC4033"/>).
     3597   the response is protected by DNSSEC (<xref target="RFC4033"/>).
    35983598</t>
    35993599</section>
Note: See TracChangeset for help on using the changeset viewer.