Changeset 2230 for draft-ietf-httpbis


Ignore:
Timestamp:
30/04/13 12:59:03 (10 years ago)
Author:
julian.reschke@…
Message:

editorial improvements (see #461)

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

Legend:

Unmodified
Added
Removed

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

    r2218 r2230  
    449449  }
    450450  @bottom-center {
    451        content: "Expires October 2013";
     451       content: "Expires November 1, 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-p4-conditional-latest">
    493       <meta name="dct.issued" scheme="ISO8601" content="2013-04">
     493      <meta name="dct.issued" scheme="ISO8601" content="2013-04-30">
    494494      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    495495      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines HTTP/1.1 conditional requests, including metadata header fields for indicating state changes, request header fields for making preconditions on such state, and rules for constructing the responses to a conditional request when one or more preconditions evaluate to false.">
    … …  
    517517            </tr>
    518518            <tr>
    519                <td class="left">Expires: October 2013</td>
    520                <td class="right">April 2013</td>
     519               <td class="left">Expires: November 1, 2013</td>
     520               <td class="right">April 30, 2013</td>
    521521            </tr>
    522522         </tbody>
    … …  
    545545         in progress”.
    546546      </p>
    547       <p>This Internet-Draft will expire in October 2013.</p>
     547      <p>This Internet-Draft will expire on November 1, 2013.</p>
    548548      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    549549      <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    … …  
    683683         data is available prior to the response header fields being sent and the digest does not need to be recalculated every time
    684684         a validation request is received. However, if a resource has distinct representations that differ only in their metadata,
    685          such as might occur with content negotiation over media types that happen to share the same data format, then the origin server <em class="bcp14">SHOULD</em> incorporate additional information in the validator to distinguish those representations and avoid confusing cache behavior.
     685         such as might occur with content negotiation over media types that happen to share the same data format, then the origin server <em class="bcp14">SHOULD</em> incorporate additional information in the validator to distinguish those representations and avoid confusing undesired behaviors
     686         (such as in caches).
    686687      </p>
    687688      <p id="rfc.section.2.1.p.6">In contrast, a "weak validator" is representation metadata that might not change for every change to the representation data.
    … …  
    969970      </p>
    970971      <p id="rfc.section.3.2.p.3">If-None-Match can also be used with a value of "*" to prevent an unsafe request method (e.g., PUT) from inadvertently modifying
    971          an existing representation of the target resource when the client believes that the resource does not have a current representation.
    972          This is a variation on the "lost update" problem that might arise if more than one client attempts to create an initial representation
    973          for the target resource.
     972         an existing representation of the target resource when the client believes that the resource does not have a current representation
     973         (<a href="p2-semantics.html#safe.methods" title="Safe Methods">Section 4.2.1</a> of <a href="#Part2" id="rfc.xref.Part2.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>). This is a variation on the "lost update" problem that might arise if more than one client attempts to create an initial
     974         representation for the target resource.
    974975      </p>
    975976      <div id="rfc.figure.u.10"></div><pre class="inline"><span id="rfc.iref.g.8"></span>  <a href="#header.if-none-match" class="smpl">If-None-Match</a> = "*" / 1#<a href="#header.etag" class="smpl">entity-tag</a>
    … …  
    12291230      <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>
    12301231      <p id="rfc.section.7.p.1">This section is meant to inform developers, information providers, and users of known security concerns specific to the HTTP/1.1
    1231          conditional request mechanisms. More general security considerations are addressed in HTTP messaging <a href="#Part1" id="rfc.xref.Part1.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a> and semantics <a href="#Part2" id="rfc.xref.Part2.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>.
     1232         conditional request mechanisms. More general security considerations are addressed in HTTP messaging <a href="#Part1" id="rfc.xref.Part1.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a> and semantics <a href="#Part2" id="rfc.xref.Part2.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>.
    12321233      </p>
    12331234      <p id="rfc.section.7.p.2">The validators defined by this specification are not intended to ensure the validity of a representation, guard against malicious
    … …  
    13321333  <a href="#imported.abnf" class="smpl">obs-text</a>      = &lt;obs-text, defined in <a href="#Part1" id="rfc.xref.Part1.9"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.6</a>&gt;
    13331334</pre><p id="rfc.section.B.p.4">The rules below are defined in other parts:</p>
    1334       <div id="rfc.figure.u.17"></div><pre class="inline">  <a href="#imported.abnf" class="smpl">HTTP-date</a>     = &lt;HTTP-date, defined in <a href="#Part2" id="rfc.xref.Part2.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>, <a href="p2-semantics.html#http.date" title="Date/Time Formats">Section 7.1.1.1</a>&gt;
     1335      <div id="rfc.figure.u.17"></div><pre class="inline">  <a href="#imported.abnf" class="smpl">HTTP-date</a>     = &lt;HTTP-date, defined in <a href="#Part2" id="rfc.xref.Part2.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>, <a href="p2-semantics.html#http.date" title="Date/Time Formats">Section 7.1.1.1</a>&gt;
    13351336</pre><h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
    13361337      <p id="rfc.section.C.p.1">In the collected ABNF below, list rules are expanded as per <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#Part1" id="rfc.xref.Part1.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.
    … …  
    14131414         </li>
    14141415         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/437">http://tools.ietf.org/wg/httpbis/trac/ticket/437</a>&gt;: "incorrect example dates"
     1416         </li>
     1417      </ul>
     1418      <p id="rfc.section.D.4.p.2">Partly resolved issues: </p>
     1419      <ul>
     1420         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/461">http://tools.ietf.org/wg/httpbis/trac/ticket/461</a>&gt;: "Editorial suggestions"
    14151421         </li>
    14161422      </ul>
    … …  
    14781484                     </ul>
    14791485                  </li>
    1480                   <li><em>Part2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.1">1</a>, <a href="#rfc.xref.Part2.2">1</a>, <a href="#rfc.xref.Part2.3">2.3.3</a>, <a href="#rfc.xref.Part2.4">2.3.3</a>, <a href="#rfc.xref.Part2.5">7</a>, <a href="#Part2"><b>9.1</b></a>, <a href="#rfc.xref.Part2.6">B</a><ul>
     1486                  <li><em>Part2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.1">1</a>, <a href="#rfc.xref.Part2.2">1</a>, <a href="#rfc.xref.Part2.3">2.3.3</a>, <a href="#rfc.xref.Part2.4">2.3.3</a>, <a href="#rfc.xref.Part2.5">3.2</a>, <a href="#rfc.xref.Part2.6">7</a>, <a href="#Part2"><b>9.1</b></a>, <a href="#rfc.xref.Part2.7">B</a><ul>
    14811487                        <li><em>Section 3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.2">1</a></li>
    14821488                        <li><em>Section 3.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.3">2.3.3</a></li>
     1489                        <li><em>Section 4.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.5">3.2</a></li>
    14831490                        <li><em>Section 5.3.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.4">2.3.3</a></li>
    1484                         <li><em>Section 7.1.1.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.6">B</a></li>
     1491                        <li><em>Section 7.1.1.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.7">B</a></li>
    14851492                     </ul>
    14861493                  </li>

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

    r2218 r2230  
    2424  <!ENTITY field-components           "<xref target='Part1' x:rel='#field.components' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    2525  <!ENTITY header-date                "<xref target='Part2' x:rel='#header.date' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     26  <!ENTITY safe-methods               "<xref target='Part2' x:rel='#safe.methods' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    2627  <!ENTITY representation             "<xref target='Part2' x:rel='#representations' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    2728  <!ENTITY messaging                  "<xref target='Part1' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    … …  
    242243   media types that happen to share the same data format, then the origin
    243244   server &SHOULD; incorporate additional information in the validator to
    244    distinguish those representations and avoid confusing cache behavior.
     245   distinguish those representations and avoid confusing undesired behaviors
     246   (such as in caches).
    245247</t>
    246248<t>
    … …  
    726728   request method (e.g., PUT) from inadvertently modifying an existing
    727729   representation of the target resource when the client believes that
    728    the resource does not have a current representation.  This is a variation
    729    on the "lost update" problem that might arise if more than one client
    730    attempts to create an initial representation for the target resource.
     730   the resource does not have a current representation (&safe-methods;).
     731   This is a variation on the "lost update" problem that might arise if more
     732   than one client attempts to create an initial representation for the target
     733   resource.
    731734</t>
    732735<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="If-None-Match"/>
    … …  
    16011604  </list>
    16021605</t>
     1606<t>
     1607  Partly resolved issues:
     1608  <list style="symbols">
     1609    <t>
     1610      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/461"/>:
     1611      "Editorial suggestions"
     1612    </t>
     1613  </list>
     1614</t>
    16031615</section>
    16041616</section>
Note: See TracChangeset for help on using the changeset viewer.