Ignore:
Timestamp:
Aug 22, 2008, 4:56:21 AM (11 years ago)
Author:
julian.reschke@…
Message:

Update orig RFCs, also add 2145 and 5234

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/orig/rfc2617.xml

    r9 r311  
    1 <?xml version="1.0" encoding="utf-8"?>
     1<?xml version="1.0" encoding="UTF-8"?>
     2<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
    23<?rfc toc="yes"?>
    34<?rfc symrefs="no"?>
     
    2021  <!ENTITY SHOULD-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHOULD NOT</bcp14>">
    2122]>
    22 <rfc number="2617" category="std" obsoletes="2069" xmlns:x='http://purl.org/net/xml2rfc/ext'>
     23<rfc number="2617" category="std" obsoletes="2069" xmlns:x='http://purl.org/net/xml2rfc/ext' xmlns:grddl='http://www.w3.org/2003/g/data-view#' grddl:transformation='rfc2629grddl.xslt'>
    2324  <front>
    2425    <title abbrev="HTTP Authentication">HTTP Authentication: Basic and Digest Access Authentication</title>
     
    147148  <middle>
    148149 
    149 <section title="Access Authentication" anchor="access.authentication">
     150<section title="Access Authentication">
    150151
    151152<section title="Reliance on the HTTP/1.1 Specification">
    152153<t>
    153154   This specification is a companion to the HTTP/1.1 specification <xref target="RFC2616"/>.
    154    It uses the augmented BNF section <xref target="RFC2616" x:fmt="number" x:sec="2.1"/> of that document, and relies on
     155   It uses the augmented BNF section <xref target="RFC2616" x:fmt="number" x:rel="#notation.abnf"/> of that document, and relies on
    155156   both the non-terminals defined in that document and other aspects of
    156157   the HTTP/1.1 specification.
     
    206207   authentication schemes that issue a challenge. The realm value
    207208   (case-sensitive), in combination with the canonical root URL (the
    208    absoluteURI for the server whose abs_path is empty; see section <xref target="RFC2616" x:fmt="number" x:sec="5.1.2"/>
     209   absoluteURI for the server whose abs_path is empty; see section <xref target="RFC2616" x:fmt="number" x:rel="#request-uri"/>
    209210   of <xref target="RFC2616"/>) of the server being accessed, defines the protection space.
    210211   These realms allow the protected resources on a server to be
     
    273274   authentication by origin servers. That is, they must forward the
    274275   WWW-Authenticate and Authorization headers untouched, and follow the
    275    rules found in section <xref target="RFC2616" x:fmt="number" x:sec="14.8"/> of <xref target="RFC2616"/>. Both the Proxy-Authenticate and
     276   rules found in section <xref target="RFC2616" x:fmt="number" x:rel="#header.authorization"/> of <xref target="RFC2616"/>. Both the Proxy-Authenticate and
    276277   the Proxy-Authorization header fields are hop-by-hop headers (see
    277    section <xref target="RFC2616" x:fmt="number" x:sec="13.5.1"/> of <xref target="RFC2616"/>).
     278   section <xref target="RFC2616" x:fmt="number" x:rel="#end-to-end.and.hop-by-hop.headers"/> of <xref target="RFC2616"/>).
    278279</t>
    279280</section>
     
    895896<t>
    896897   The "Method" value is the HTTP request method as specified in section
    897    <xref target="RFC2616" x:fmt="number" x:sec="5.1.1"/> of <xref target="RFC2616"/>. The "request-uri" value is the Request-URI from the
    898    request line as specified in section <xref target="RFC2616" x:fmt="number" x:sec="5.1.2"/> of <xref target="RFC2616"/>. This may be "*",
    899    an "absoluteURL" or an "abs_path" as specified in section <xref target="RFC2616" x:fmt="number" x:sec="5.1.2"/> of
     898   <xref target="RFC2616" x:fmt="number" x:rel="#method"/> of <xref target="RFC2616"/>. The "request-uri" value is the Request-URI from the
     899   request line as specified in section <xref target="RFC2616" x:fmt="number" x:rel="#request-uri"/> of <xref target="RFC2616"/>. This may be "*",
     900   an "absoluteURL" or an "abs_path" as specified in section <xref target="RFC2616" x:fmt="number" x:rel="#request-uri"/> of
    900901   <xref target="RFC2616"/>, but it &MUST; agree with the Request-URI. In particular, it &MUST;
    901902   be an "absoluteURL" if the Request-URI is an "absoluteURL". The
     
    918919   Implementers should be aware of how authenticated transactions
    919920   interact with shared caches. The HTTP/1.1 protocol specifies that
    920    when a shared cache (see section <xref target="RFC2616" x:fmt="number" x:sec="13.7"/> of <xref target="RFC2616"/>) has received a request
     921   when a shared cache (see section <xref target="RFC2616" x:fmt="number" x:rel="#shared.and.non-shared.caches"/> of <xref target="RFC2616"/>) has received a request
    921922   containing an Authorization header and a response from relaying that
    922923   request, it &MUST-NOT; return that response as a reply to any other
    923    request, unless one of two Cache-Control (see section <xref target="RFC2616" x:fmt="number" x:sec="14.9"/> of <xref target="RFC2616"/>)
     924   request, unless one of two Cache-Control (see section <xref target="RFC2616" x:fmt="number" x:rel="#header.cache-control"/> of <xref target="RFC2616"/>)
    924925   directives was present in the response. If the original response
    925926   included the "must-revalidate" Cache-Control directive, the cache &MAY;
     
    12701271   period of time or number of uses, or any other restrictions.  Doing
    12711272   so strengthens the protection provided against, for example, replay
    1272    attacks (see 4.5).  However, it should be noted that the method
     1273   attacks (see <xref target="replay.attacks" format="counter"/>).  However, it should be noted that the method
    12731274   chosen for generating and checking the nonce also has performance and
    12741275   resource implications.  For example, a server may choose to allow
     
    13131314</section>
    13141315
    1315 <section title="Replay Attacks">
     1316<section title="Replay Attacks" anchor="replay.attacks">
    13161317<t>
    13171318   A replay attack against Digest authentication would usually be
     
    19051906</front>
    19061907<seriesInfo name="RFC" value="2616"/>
     1908
     1909  <x:source href="rfc2616.xml"/>
    19071910</reference>
    19081911
Note: See TracChangeset for help on using the changeset viewer.