Ignore:
Timestamp:
May 8, 2009, 8:02:25 AM (11 years ago)
Author:
julian.reschke@…
Message:

editorial: removed an unnecessary reference to RFC 2068, made another one more specific

File:
1 edited

Legend:

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

    r576 r578  
    17761776   these performance problems and results from a prototype
    17771777   implementation are available <xref target="Pad1995"/> <xref target="Spe"/>. Implementation experience and
    1778    measurements of actual HTTP/1.1 (<xref target="RFC2068" x:fmt="none">RFC 2068</xref>) implementations show good
     1778   measurements of actual HTTP/1.1 implementations show good
    17791779   results <xref target="Nie1997"/>. Alternatives have also been explored, for example,
    17801780   T/TCP <xref target="Tou1998"/>.
     
    19091909<t>
    19101910   A proxy server &MUST-NOT; establish a HTTP/1.1 persistent connection
    1911    with an HTTP/1.0 client (but see <xref target="RFC2068"/> for information and
    1912    discussion of the problems with the Keep-Alive header implemented by
    1913    many HTTP/1.0 clients).
     1911   with an HTTP/1.0 client (but see <xref x:sec="19.7.1" x:fmt="of" target="RFC2068"/>
     1912   for information and discussion of the problems with the Keep-Alive header
     1913   implemented by many HTTP/1.0 clients).
    19141914</t>
    19151915</section>
     
    40094009<t>
    40104010   The original HTTP/1.0 form of persistent connections (the Connection:
    4011    Keep-Alive and Keep-Alive header) is documented in <xref target="RFC2068"/>.
     4011   Keep-Alive and Keep-Alive header) is documented in <xref x:sec="19.7.1" x:fmt="of" target="RFC2068"/>.
    40124012</t>
    40134013</section>
Note: See TracChangeset for help on using the changeset viewer.