Changeset 2227


Ignore:
Timestamp:
Apr 25, 2013, 7:25:26 AM (6 years ago)
Author:
julian.reschke@…
Message:

augment considerations for new header fields

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

Legend:

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

    r2223 r2227  
    449449  }
    450450  @bottom-center {
    451        content: "Expires October 21, 2013";
     451       content: "Expires October 27, 2013";
    452452  }
    453453  @bottom-right {
     
    494494      <meta name="dct.creator" content="Reschke, J. F.">
    495495      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
    496       <meta name="dct.issued" scheme="ISO8601" content="2013-04-19">
     496      <meta name="dct.issued" scheme="ISO8601" content="2013-04-25">
    497497      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    498498      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines the semantics of HTTP/1.1 messages, as expressed by request methods, request header fields, response status codes, and response header fields, along with the payload of messages (metadata and body content) and mechanisms for content negotiation.">
     
    522522            <tr>
    523523               <td class="left">Intended status: Standards Track</td>
    524                <td class="right">April 19, 2013</td>
     524               <td class="right">April 25, 2013</td>
    525525            </tr>
    526526            <tr>
    527                <td class="left">Expires: October 21, 2013</td>
     527               <td class="left">Expires: October 27, 2013</td>
    528528               <td class="right"></td>
    529529            </tr>
     
    553553         in progress”.
    554554      </p>
    555       <p>This Internet-Draft will expire on October 21, 2013.</p>
     555      <p>This Internet-Draft will expire on October 27, 2013.</p>
    556556      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    557557      <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    36183618         </li>
    36193619         <li>
     3620            <p>Whether the field should be stored by origin servers that understand it upon a PUT request.</p>
     3621         </li>
     3622         <li>
    36203623            <p>Whether the field semantics are further refined by the context, such as by existing request methods or status codes.</p>
    36213624         </li>
     
    36283631         </li>
    36293632         <li>
    3630             <p>How the header field might interact with caching (see <a href="#Part6" id="rfc.xref.Part6.29"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
     3633            <p>That when the header is used in requests and affects response selection (<a href="p6-cache.html#caching.negotiated.responses" title="Using Negotiated Responses">Section 4.3</a> of <a href="#Part6" id="rfc.xref.Part6.29"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>), it ought to be listed in the <a href="#header.vary" class="smpl">Vary</a> response header field (<a href="#header.vary" id="rfc.xref.header.vary.3" title="Vary">Section&nbsp;7.1.4</a>).
    36313634            </p>
    36323635         </li>
     
    37903793                  <td class="left">http</td>
    37913794                  <td class="left">standard</td>
    3792                   <td class="left"> <a href="#header.vary" id="rfc.xref.header.vary.3" title="Vary">Section&nbsp;7.1.4</a>
     3795                  <td class="left"> <a href="#header.vary" id="rfc.xref.header.vary.4" title="Vary">Section&nbsp;7.1.4</a>
    37933796                  </td>
    37943797               </tr>
     
    47204723                        <li><em>Section 4.1.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.5">4.3.3</a></li>
    47214724                        <li><em>Section 4.1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.11">6.3.1</a>, <a href="#rfc.xref.Part6.13">6.3.4</a>, <a href="#rfc.xref.Part6.14">6.3.5</a>, <a href="#rfc.xref.Part6.15">6.4.1</a>, <a href="#rfc.xref.Part6.16">6.4.2</a>, <a href="#rfc.xref.Part6.17">6.5.4</a>, <a href="#rfc.xref.Part6.18">6.5.5</a>, <a href="#rfc.xref.Part6.19">6.5.9</a>, <a href="#rfc.xref.Part6.20">6.5.12</a>, <a href="#rfc.xref.Part6.21">6.6.2</a></li>
    4722                         <li><em>Section 4.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.26">7.1.4</a></li>
     4725                        <li><em>Section 4.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.26">7.1.4</a>, <a href="#rfc.xref.Part6.29">8.3.1</a></li>
    47234726                        <li><em>Section 5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.4">4.3.2</a></li>
    47244727                        <li><em>Section 6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.6">4.3.4</a>, <a href="#rfc.xref.Part6.7">4.3.5</a></li>
     
    48514854            </li>
    48524855            <li><a id="rfc.index.V" href="#rfc.index.V"><b>V</b></a><ul>
    4853                   <li>Vary header field&nbsp;&nbsp;<a href="#rfc.xref.header.vary.1">3.4.1</a>, <a href="#rfc.xref.header.vary.2">7.1</a>, <a href="#rfc.iref.v.1"><b>7.1.4</b></a>, <a href="#rfc.xref.header.vary.3">8.3.2</a></li>
     4856                  <li>Vary header field&nbsp;&nbsp;<a href="#rfc.xref.header.vary.1">3.4.1</a>, <a href="#rfc.xref.header.vary.2">7.1</a>, <a href="#rfc.iref.v.1"><b>7.1.4</b></a>, <a href="#rfc.xref.header.vary.3">8.3.1</a>, <a href="#rfc.xref.header.vary.4">8.3.2</a></li>
    48544857               </ul>
    48554858            </li>
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r2223 r2227  
    46424642      responses or requests, in all messages, only on responses to a
    46434643      particular request method, etc.</t></x:lt>
     4644    <x:lt><t>Whether the field should be stored by origin servers that
     4645      understand it upon a PUT request.</t></x:lt>
    46444646    <x:lt><t>Whether the field semantics are further refined by the context,
    46454647      such as by existing request methods or status codes.</t></x:lt>
     
    46494651    <x:lt><t>Under what conditions intermediaries are allowed to insert,
    46504652      delete, or modify the field's value.</t></x:lt>
    4651     <x:lt><t>How the header field might interact with caching (see
    4652       <xref target="Part6"/>).</t></x:lt>
     4653    <x:lt><t>That when the header is used in requests and affects response
     4654      selection (&caching-neg-resp;), it ought to be listed in the
     4655      <x:ref>Vary</x:ref> response header field (<xref target="header.vary"/>).</t></x:lt>
    46534656    <x:lt><t>Whether the header field is useful or allowable in trailers (see
    46544657      &chunked-encoding;).</t></x:lt>
Note: See TracChangeset for help on using the changeset viewer.