Changeset 39


Ignore:
Timestamp:
Dec 17, 2007, 4:22:08 PM (11 years ago)
Author:
fielding@…
Message:

move the p1 top-level sections "206 Partial Content" and
"416 Requested Range Not Satisfiable" into a common section
"Status Code Definitions".

Also add that top-level section to p7, and move 401 and 407 there.

Submitted by: Julian Reschke

Location:
draft-ietf-httpbis/latest
Files:
3 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r38 r39  
    13141314  <iref primary="true" item="Status Codes" subitem="401 Unauthorized" x:for-anchor=""/>
    13151315<t>
    1316    The request requires user authentication. The response &MUST; include a
    1317    WWW-Authenticate header field (&header-www-authenticate;) containing a challenge
    1318    applicable to the requested resource. The client &MAY; repeat the
    1319    request with a suitable Authorization header field (&header-authorization;). If
    1320    the request already included Authorization credentials, then the 401
    1321    response indicates that authorization has been refused for those
    1322    credentials. If the 401 response contains the same challenge as the
    1323    prior response, and the user agent has already attempted
    1324    authentication at least once, then the user &SHOULD; be presented the
    1325    entity that was given in the response, since that entity might
    1326    include relevant diagnostic information. HTTP access authentication
    1327    is explained in "HTTP Authentication: Basic and Digest Access
    1328    Authentication" <xref target="RFC2617"/>.
     1316   The request requires user authentication (see &auth;).
    13291317</t>
    13301318</section>
     
    14151403<t>
    14161404   This code is similar to 401 (Unauthorized), but indicates that the
    1417    client must first authenticate itself with the proxy. The proxy &MUST;
    1418    return a Proxy-Authenticate header field (&header-proxy-authenticate;) containing a
    1419    challenge applicable to the proxy for the requested resource. The
    1420    client &MAY; repeat the request with a suitable Proxy-Authorization
    1421    header field (&header-proxy-authorization;). HTTP access authentication is explained
    1422    in "HTTP Authentication: Basic and Digest Access Authentication"
    1423    <xref target="RFC2617"/>.
     1405   client must first authenticate itself with the proxy (see &auth;).
    14241406</t>
    14251407</section>
  • draft-ietf-httpbis/latest/p5-range.xml

    r36 r39  
    209209</section>
    210210
     211<section title="Status Code Definitions">
    211212<section title="206 Partial Content" anchor="status.206">
    212213  <iref primary="true" item="206 Partial Content (status code)" x:for-anchor=""/>
     
    282283   This response &MUST-NOT; use the multipart/byteranges content-type.
    283284</t>
     285</section>
    284286</section>
    285287
  • draft-ietf-httpbis/latest/p7-auth.xml

    r36 r39  
    192192</t>
    193193</section>
     194
     195<section title="Status Code Definitions">
     196<section title="401 Unauthorized" anchor="status.401">
     197  <iref primary="true" item="401 Unauthorized (status code)" x:for-anchor=""/>
     198  <iref primary="true" item="Status Codes" subitem="401 Unauthorized" x:for-anchor=""/>
     199<t>
     200   The request requires user authentication. The response &MUST; include a
     201   WWW-Authenticate header field (<xref target="header.www-authenticate"/>) containing a challenge
     202   applicable to the requested resource. The client &MAY; repeat the
     203   request with a suitable Authorization header field (<xref target="header.authorization"/>). If
     204   the request already included Authorization credentials, then the 401
     205   response indicates that authorization has been refused for those
     206   credentials. If the 401 response contains the same challenge as the
     207   prior response, and the user agent has already attempted
     208   authentication at least once, then the user &SHOULD; be presented the
     209   entity that was given in the response, since that entity might
     210   include relevant diagnostic information. HTTP access authentication
     211   is explained in "HTTP Authentication: Basic and Digest Access
     212   Authentication" <xref target="RFC2617"/>.
     213</t>
     214</section>
     215<section title="407 Proxy Authentication Required" anchor="status.407">
     216  <iref primary="true" item="407 Proxy Authentication Required (status code)" x:for-anchor=""/>
     217  <iref primary="true" item="Status Codes" subitem="407 Proxy Authentication Required" x:for-anchor=""/>
     218<t>
     219   This code is similar to 401 (Unauthorized), but indicates that the
     220   client must first authenticate itself with the proxy. The proxy &MUST;
     221   return a Proxy-Authenticate header field (<xref target="header.proxy-authenticate"/>) containing a
     222   challenge applicable to the proxy for the requested resource. The
     223   client &MAY; repeat the request with a suitable Proxy-Authorization
     224   header field (<xref target="header.proxy-authorization"/>). HTTP access authentication is explained
     225   in "HTTP Authentication: Basic and Digest Access Authentication"
     226   <xref target="RFC2617"/>.
     227</t>
     228</section>
     229</section>
     230
    194231<section title="Header Field Definitions" anchor="header.fields">
    195232<t>
Note: See TracChangeset for help on using the changeset viewer.