Changeset 1734 for draft-ietf-httpbis


Ignore:
Timestamp:
06/07/12 13:59:02 (10 years ago)
Author:
julian.reschke@…
Message:

Work-in-progress: hyperlink status codes definitions (P4)

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

Legend:

Unmodified
Added
Removed

  • draft-ietf-httpbis/latest/p1-messaging.html

    r1727 r1734  
    449449  }
    450450  @bottom-center {
    451        content: "Expires January 6, 2013";
     451       content: "Expires January 7, 2013";
    452452  }
    453453  @bottom-right {
    … …  
    491491      <meta name="dct.creator" content="Reschke, J. F.">
    492492      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest">
    493       <meta name="dct.issued" scheme="ISO8601" content="2012-07-05">
     493      <meta name="dct.issued" scheme="ISO8601" content="2012-07-06">
    494494      <meta name="dct.replaces" content="urn:ietf:rfc:2145">
    495495      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    … …  
    523523            </tr>
    524524            <tr>
    525                <td class="left">Expires: January 6, 2013</td>
     525               <td class="left">Expires: January 7, 2013</td>
    526526               <td class="right">greenbytes</td>
    527527            </tr>
    528528            <tr>
    529529               <td class="left"></td>
    530                <td class="right">July 5, 2012</td>
     530               <td class="right">July 6, 2012</td>
    531531            </tr>
    532532         </tbody>
    … …  
    561561         in progress”.
    562562      </p>
    563       <p>This Internet-Draft will expire on January 6, 2013.</p>
     563      <p>This Internet-Draft will expire on January 7, 2013.</p>
    564564      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    565565      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    … …  
    14201420      <p id="rfc.section.3.3.2.p.1">When a message does not have a Transfer-Encoding header field and the payload body length can be determined prior to being
    14211421         transferred, a Content-Length header field <em class="bcp14">SHOULD</em> be sent to indicate the length of the payload body that is either present as the message body, for requests and non-HEAD responses
    1422          other than 304, or would have been present had the request been an unconditional GET. The length is expressed as a decimal
    1423          number of octets.
     1422         other than <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a>, or would have been present had the request been an unconditional GET. The length is expressed as a decimal number of octets.
    14241423      </p>
    14251424      <div id="rfc.figure.u.35"></div><pre class="inline"><span id="rfc.iref.g.53"></span>  <a href="#header.content-length" class="smpl">Content-Length</a> = 1*<a href="#core.rules" class="smpl">DIGIT</a>
    … …  
    14461445      <ol>
    14471446         <li>
    1448             <p>Any response to a HEAD request and any response with a status code of 100-199, 204, or 304 is always terminated by the first
    1449                empty line after the header fields, regardless of the header fields present in the message, and thus cannot contain a message
    1450                body.
     1447            <p>Any response to a HEAD request and any response with a status code of 100-199, 204, or <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a> is always terminated by the first empty line after the header fields, regardless of the header fields present in the message,
     1448               and thus cannot contain a message body.
    14511449            </p>
    14521450         </li>

  • draft-ietf-httpbis/latest/p1-messaging.xml

    r1727 r1734  
    15871587   Content-Length header field &SHOULD; be sent to indicate the length of the
    15881588   payload body that is either present as the message body, for requests
    1589    and non-HEAD responses other than 304, or would have been present had
    1590    the request been an unconditional GET.  The length is expressed as a
    1591    decimal number of octets.
     1589   and non-HEAD responses other than <x:ref>304 (Not Modified)</x:ref>, or
     1590   would have been present had the request been an unconditional GET.  The
     1591   length is expressed as a decimal number of octets.
    15921592</t>
    15931593<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Content-Length"/>
    … …  
    16441644    <x:lt><t>
    16451645     Any response to a HEAD request and any response with a status
    1646      code of 100-199, 204, or 304 is always terminated by the first
    1647      empty line after the header fields, regardless of the header
    1648      fields present in the message, and thus cannot contain a message body.
     1646     code of 100-199, 204, or <x:ref>304 (Not Modified)</x:ref> is always
     1647     terminated by the first empty line after the header fields, regardless of
     1648     the header fields present in the message, and thus cannot contain a
     1649     message body.
    16491650    </t></x:lt>
    16501651    <x:lt><t>

  • draft-ietf-httpbis/latest/p2-semantics.html

    r1732 r1734  
    23882388      </p>
    23892389      <ol>
    2390          <li>If the response status code is 200 or 203 and the request method was GET, the response payload is a representation of the
    2391             target resource.
    2392          </li>
    2393          <li>If the response status code is 204, <a href="p5-range.html#status.206" class="smpl">206</a>, or 304 and the request method was GET or HEAD, the response payload is a partial representation of the target resource.
     2390         <li>If the response status code is <a href="#status.200" class="smpl">200 (OK)</a> or <a href="#status.203" class="smpl">203
     2391               (Non-Authoritative Information)</a> and the request method was GET, the response payload is a representation of the target resource.
     2392         </li>
     2393         <li>If the response status code is <a href="#status.204" class="smpl">204 (No Content)</a>, 206 (Partial Content, or <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a> and the request method was GET or HEAD, the response payload is a partial representation of the target resource.
    23942394         </li>
    23952395         <li>If the response has a Content-Location header field, and that URI is the same as the effective request URI, the response payload

  • draft-ietf-httpbis/latest/p2-semantics.xml

    r1732 r1734  
    27042704</t>
    27052705<t><list style="numbers">
    2706    <t>If the response status code is 200 or 203 and the request method was GET,
     2706   <t>If the response status code is <x:ref>200 (OK)</x:ref> or <x:ref>203
     2707   (Non-Authoritative Information)</x:ref> and the request method was GET,
    27072708   the response payload is a representation of the target resource.</t>
    2708    <t>If the response status code is 204, <x:ref>206</x:ref>, or 304 and the request method was GET
    2709    or HEAD, the response payload is a partial representation of the target
    2710    resource.</t>
     2709   <t>If the response status code is <x:ref>204 (No Content)</x:ref>,
     2710   <x:ref>206 (Partial Content</x:ref>, or <x:ref>304 (Not Modified)</x:ref>
     2711   and the request method was GET or HEAD, the response payload is a partial
     2712   representation of the target resource.</t>
    27112713   <t>If the response has a Content-Location header field, and that URI is the same
    27122714   as the effective request URI, the response payload is a representation of the

  • draft-ietf-httpbis/latest/p4-conditional.html

    r1733 r1734  
    991991         they <em class="bcp14">MUST</em> forward the request towards the origin server.
    992992      </p>
    993       <p id="rfc.section.3.1.p.6">If the request would, without the If-Match header field, result in anything other than a <a href="p2-semantics.html#status.2xx" class="smpl">2xx</a> or 412 status code, then the If-Match header field <em class="bcp14">MUST</em> be ignored.
     993      <p id="rfc.section.3.1.p.6">If the request would, without the If-Match header field, result in anything other than a <a href="p2-semantics.html#status.2xx" class="smpl">2xx (Successful)</a> or <a href="#status.412" class="smpl">412 (Precondition Failed)</a> status code, then the If-Match header field <em class="bcp14">MUST</em> be ignored.
    994994      </p>
    995995      <p id="rfc.section.3.1.p.7">Examples:</p>
    … …  
    10071007         updates of cached information with a minimum amount of transaction overhead. A client that has one or more representations
    10081008         previously obtained from the target resource can send If-None-Match with a list of the associated entity-tags in the hope
    1009          of receiving a 304 response if at least one of those representations matches the selected representation.
     1009         of receiving a <a href="#status.304" class="smpl">304 (Not Modified)</a> response if at least one of those representations matches the selected representation.
    10101010      </p>
    10111011      <p id="rfc.section.3.2.p.2">If-None-Match can also be used with a value of "*" to prevent an unsafe request method (e.g., PUT) from inadvertently modifying
    … …  
    10211021      <p id="rfc.section.3.2.p.5">If none of the entity-tags match, then the server <em class="bcp14">MAY</em> perform the requested method as if the If-None-Match header field did not exist, but <em class="bcp14">MUST</em> also ignore any If-Modified-Since header field(s) in the request. That is, if no entity-tags match, then the server <em class="bcp14">MUST NOT</em> return a <a href="#status.304" class="smpl">304 (Not Modified)</a> response.
    10221022      </p>
    1023       <p id="rfc.section.3.2.p.6">If the request would, without the If-None-Match header field, result in anything other than a <a href="p2-semantics.html#status.2xx" class="smpl">2xx</a> or 304 status code, then the If-None-Match header field <em class="bcp14">MUST</em> be ignored. (See <a href="#rules.for.when.to.use.entity.tags.and.last-modified.dates" title="Rules for When to Use Entity-tags and Last-Modified Dates">Section&nbsp;2.4</a> for a discussion of server behavior when both If-Modified-Since and If-None-Match appear in the same request.)
     1023      <p id="rfc.section.3.2.p.6">If the request would, without the If-None-Match header field, result in anything other than a <a href="p2-semantics.html#status.2xx" class="smpl">2xx (Successful)</a> or <a href="#status.304" class="smpl">304 (Not Modified)</a> status code, then the If-None-Match header field <em class="bcp14">MUST</em> be ignored. (See <a href="#rules.for.when.to.use.entity.tags.and.last-modified.dates" title="Rules for When to Use Entity-tags and Last-Modified Dates">Section&nbsp;2.4</a> for a discussion of server behavior when both If-Modified-Since and If-None-Match appear in the same request.)
    10241024      </p>
    10251025      <p id="rfc.section.3.2.p.7">Examples:</p>
    … …  
    10871087</pre><p id="rfc.section.3.4.p.3">An example of the field is:</p>
    10881088      <div id="rfc.figure.u.16"></div><pre class="text">  If-Unmodified-Since: Sat, 29 Oct 1994 19:43:31 GMT
    1089 </pre><p id="rfc.section.3.4.p.5">If a request normally (i.e., in absence of the If-Unmodified-Since header field) would result in anything other than a <a href="p2-semantics.html#status.2xx" class="smpl">2xx</a> or 412 status code, the If-Unmodified-Since header field <em class="bcp14">SHOULD</em> be ignored.
     1089</pre><p id="rfc.section.3.4.p.5">If a request normally (i.e., in absence of the If-Unmodified-Since header field) would result in anything other than a <a href="p2-semantics.html#status.2xx" class="smpl">2xx (Successful)</a> or <a href="#status.412" class="smpl">412 (Precondition Failed)</a> status code, the If-Unmodified-Since header field <em class="bcp14">SHOULD</em> be ignored.
    10901090      </p>
    10911091      <p id="rfc.section.3.4.p.6">If the specified date is invalid, the header field <em class="bcp14">MUST</em> be ignored.

  • draft-ietf-httpbis/latest/p4-conditional.xml

    r1733 r1734  
    769769<t>
    770770   If the request would, without the If-Match header field, result in
    771    anything other than a <x:ref>2xx</x:ref> or 412 status code, then the If-Match header field
    772    &MUST; be ignored.
     771   anything other than a <x:ref>2xx (Successful)</x:ref> or <x:ref>412 (Precondition Failed)</x:ref>
     772   status code, then the If-Match header field &MUST; be ignored.
    773773</t>
    774774<t>
    … …  
    799799   that has one or more representations previously obtained from the
    800800   target resource can send If-None-Match with a list of the associated
    801    entity-tags in the hope of receiving a 304 response if at least one
    802    of those representations matches the selected representation.
     801   entity-tags in the hope of receiving a <x:ref>304 (Not Modified)</x:ref>
     802   response if at least one of those representations matches the selected
     803   representation.
    803804</t>
    804805<t>
    … …  
    834835<t>
    835836   If the request would, without the If-None-Match header field, result
    836    in anything other than a <x:ref>2xx</x:ref> or 304 status code, then the If-None-Match
     837   in anything other than a <x:ref>2xx (Successful)</x:ref> or
     838   <x:ref>304 (Not Modified)</x:ref> status code, then the If-None-Match
    837839   header field &MUST; be ignored. (See <xref
    838840   target="rules.for.when.to.use.entity.tags.and.last-modified.dates"/> for
    … …  
    965967<t>
    966968   If a request normally (i.e., in absence of the If-Unmodified-Since
    967    header field) would result in anything other than a <x:ref>2xx</x:ref> or 412 status code,
     969   header field) would result in anything other than a <x:ref>2xx (Successful)</x:ref>
     970   or <x:ref>412 (Precondition Failed)</x:ref> status code,
    968971   the If-Unmodified-Since header field &SHOULD; be ignored.
    969972</t>
    … …  
    992995  <iref primary="true" item="304 Not Modified (status code)" x:for-anchor=""/>
    993996  <iref primary="true" item="Status Codes" subitem="304 Not Modified" x:for-anchor=""/>
     997  <x:anchor-alias value="304"/>
    994998  <x:anchor-alias value="304 (Not Modified)"/>
    995999<t>
    … …  
    11961200  <x:source href="p2-semantics.xml" basename="p2-semantics">
    11971201    <x:defines>2xx</x:defines>
     1202    <x:defines>2xx (Successful)</x:defines>
    11981203    <x:defines>200 (OK)</x:defines>
    11991204  </x:source>

  • draft-ietf-httpbis/latest/p5-range.html

    r1732 r1734  
    987987         <li>The presence of a Range header field in a conditional GET (a request using one or both of If-Modified-Since and If-None-Match,
    988988            or one or both of If-Unmodified-Since and If-Match) modifies what is returned if the GET is otherwise successful and the condition
    989             is true. It does not affect the 304 (Not Modified) response returned if the conditional is false.
     989            is true. It does not affect the <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a> response returned if the conditional is false.
    990990         </li>
    991991      </ul>

  • draft-ietf-httpbis/latest/p5-range.xml

    r1732 r1734  
    840840        one or both of If-Unmodified-Since and If-Match) modifies what
    841841        is returned if the GET is otherwise successful and the
    842         condition is true. It does not affect the 304 (Not Modified)
     842        condition is true. It does not affect the <x:ref>304 (Not Modified)</x:ref>
    843843        response returned if the conditional is false.</t>
    844844  </list>
    … …  
    10441044  </front>
    10451045  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p4-conditional-&ID-VERSION;"/>
    1046   <x:source href="p4-conditional.xml" basename="p4-conditional"/>
     1046  <x:source href="p4-conditional.xml" basename="p4-conditional">
     1047    <x:defines>304 (Not Modified)</x:defines>
     1048  </x:source>
    10471049</reference>
    10481050

  • draft-ietf-httpbis/latest/p6-cache.html

    r1732 r1734  
    10991099      <h3 id="rfc.section.2.4.1"><a href="#rfc.section.2.4.1">2.4.1</a>&nbsp;<a id="freshening.responses" href="#freshening.responses">Freshening Responses with 304 Not Modified</a></h3>
    11001100      <p id="rfc.section.2.4.1.p.1">When a cache receives a <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a> response and already has one or more stored <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> responses for the same cache key, the cache needs to identify which of the stored responses are updated by this new response
    1101          and then update the stored response(s) with the new information provided in the 304 response.
     1101         and then update the stored response(s) with the new information provided in the <a href="p4-conditional.html#status.304" class="smpl">304</a> response.
    11021102      </p>
    11031103      <ul>
    … …  
    11191119         </li>
    11201120         <li>retain any Warning header fields in the stored response with warn-code 2xx; and,</li>
    1121          <li>use other header fields provided in the 304 response to replace all instances of the corresponding header fields in the stored
    1122             response.
     1121         <li>use other header fields provided in the <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a> response to replace all instances of the corresponding header fields in the stored response.
    11231122         </li>
    11241123      </ul>

  • draft-ietf-httpbis/latest/p6-cache.xml

    r1732 r1734  
    938938   to identify which of the stored responses are updated by this new response
    939939   and then update the stored response(s) with the new information provided in
    940    the 304 response.
     940   the <x:ref>304</x:ref> response.
    941941   <list style="symbols">
    942942    <t>
    … …  
    967967      <t>retain any Warning header fields in the stored response with
    968968         warn-code 2xx; and,</t>
    969       <t>use other header fields provided in the 304 response to replace
    970          all instances of the corresponding header fields in the stored
    971          response.</t>
     969      <t>use other header fields provided in the <x:ref>304 (Not Modified)</x:ref>
     970         response to replace all instances of the corresponding header
     971         fields in the stored response.</t>
    972972   </list>
    973973</t>
    … …  
    23212321    <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p4-conditional-&ID-VERSION;" />
    23222322    <x:source basename="p4-conditional" href="p4-conditional.xml">
     2323      <x:defines>304</x:defines>
    23232324      <x:defines>304 (Not Modified)</x:defines>
    23242325    </x:source>
Note: See TracChangeset for help on using the changeset viewer.