Ignore:
Timestamp:
08/05/14 13:46:33 (6 years ago)
Author:
julian.reschke@…
Message:

min. fixes (reg names, punctuation, etc) (see #553)

File:
1 edited

Legend:

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

    r2659 r2660  
    993993                  </p>
    994994                  <div id="rfc.figure.u.7"></div><pre class="inline"><span id="rfc.iref.g.8"></span>  <a href="#content.codings" class="smpl">content-coding</a>   = <a href="#imported.abnf" class="smpl">token</a>
    995 </pre><p id="rfc.section.3.1.2.1.p.3">All content-coding values are case-insensitive and ought to be registered within the HTTP Content Coding registry, as defined
     995</pre><p id="rfc.section.3.1.2.1.p.3">All content-coding values are case-insensitive and ought to be registered within the "HTTP Content Coding Registry", as defined
    996996                     in <a href="#content.coding.registry" title="Content Coding Registry">Section&nbsp;8.4</a>. They are used in the <a href="#header.accept-encoding" class="smpl">Accept-Encoding</a> (<a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.1" title="Accept-Encoding">Section&nbsp;5.3.4</a>) and <a href="#header.content-encoding" class="smpl">Content-Encoding</a> (<a href="#header.content-encoding" id="rfc.xref.header.content-encoding.2" title="Content-Encoding">Section&nbsp;3.1.2.2</a>) header fields.
    997997                  </p>
     
    13811381            </p>
    13821382            <p id="rfc.section.4.1.p.8">Additional methods, outside the scope of this specification, have been standardized for use in HTTP. All such methods ought
    1383                to be registered within the HTTP Method Registry maintained by IANA, as defined in <a href="#method.registry" title="Method Registry">Section&nbsp;8.1</a>.
     1383               to be registered within the "Hypertext Transfer Protocol (HTTP) Method Registry" maintained by IANA, as defined in <a href="#method.registry" title="Method Registry">Section&nbsp;8.1</a>.
    13841384            </p>
    13851385            <p id="rfc.section.4.1.p.9">The set of methods allowed by a target resource can be listed in an <a href="#header.allow" class="smpl">Allow</a> header field (<a href="#header.allow" id="rfc.xref.header.allow.1" title="Allow">Section&nbsp;7.4.1</a>). However, the set of allowed methods can change dynamically. When a request method is received that is unrecognized or not
     
    13971397                  method is not expected to cause any harm, loss of property, or unusual burden on the origin server.
    13981398               </p>
    1399                <p id="rfc.section.4.2.1.p.2">This definition of safe methods does not prevent an implementation from including behavior that is potentially harmful, not
    1400                   entirely read-only, or which causes side effects while invoking a safe method. What is important, however, is that the client
    1401                   did not request that additional behavior and cannot be held accountable for it. For example, most servers append request information
    1402                   to access log files at the completion of every response, regardless of the method, and that is considered safe even though
    1403                   the log storage might become full and crash the server. Likewise, a safe request initiated by selecting an advertisement on
    1404                   the Web will often have the side effect of charging an advertising account.
     1399               <p id="rfc.section.4.2.1.p.2">This definition of safe methods does not prevent an implementation from including behavior that is potentially harmful, that
     1400                  is not entirely read-only, or that causes side effects while invoking a safe method. What is important, however, is that the
     1401                  client did not request that additional behavior and cannot be held accountable for it. For example, most servers append request
     1402                  information to access log files at the completion of every response, regardless of the method, and that is considered safe
     1403                  even though the log storage might become full and crash the server. Likewise, a safe request initiated by selecting an advertisement
     1404                  on the Web will often have the side effect of charging an advertising account.
    14051405               </p>
    14061406               <p id="rfc.section.4.2.1.p.3">Of the request methods defined by this specification, the GET, HEAD, OPTIONS, and TRACE methods are defined to be safe.</p>
     
    22942294            </p>
    22952295            <p id="rfc.section.6.1.p.2">Responses with status codes that are defined as cacheable by default (e.g., 200, 203, 204, 206, 300, 301, 404, 405, 410, 414,
    2296                501 in this specification) can be reused by a cache with heuristic expiration unless otherwise indicated by the method definition
    2297                or explicit cache controls <a href="#RFC7234" id="rfc.xref.RFC7234.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[RFC7234]</cite></a>; all other status codes are not cacheable by default.
     2296               and 501 in this specification) can be reused by a cache with heuristic expiration unless otherwise indicated by the method
     2297               definition or explicit cache controls <a href="#RFC7234" id="rfc.xref.RFC7234.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[RFC7234]</cite></a>; all other status codes are not cacheable by default.
    22982298            </p>
    22992299            <div id="rfc.table.u.9">
     
    27242724               </p>
    27252725               <div class="note" id="rfc.section.6.4.1.p.5">
    2726                   <p><b>Note:</b> The original proposal for 300 defined the URI header field as providing a list of alternative representations, such that it
    2727                      would be usable for 200, 300, and 406 responses and be transferred in responses to the HEAD method. However, lack of deployment
    2728                      and disagreement over syntax led to both URI and Alternates (a subsequent proposal) being dropped from this specification.
    2729                      It is possible to communicate the list using a set of Link header fields <a href="#RFC5988" id="rfc.xref.RFC5988.1"><cite title="Web Linking">[RFC5988]</cite></a>, each with a relationship of "alternate", though deployment is a chicken-and-egg problem.
     2726                  <p><b>Note:</b> The original proposal for the 300 status code defined the URI header field as providing a list of alternative representations,
     2727                     such that it would be usable for 200, 300, and 406 responses and be transferred in responses to the HEAD method. However,
     2728                     lack of deployment and disagreement over syntax led to both URI and Alternates (a subsequent proposal) being dropped from
     2729                     this specification. It is possible to communicate the list using a set of Link header fields <a href="#RFC5988" id="rfc.xref.RFC5988.1"><cite title="Web Linking">[RFC5988]</cite></a>, each with a relationship of "alternate", though deployment is a chicken-and-egg problem.
    27302730                  </p>
    27312731               </div>
     
    34563456                  value of "0".
    34573457               </p>
    3458                <p id="rfc.section.8.1.2.p.3">A new method definition needs to indicate whether it is safe (<a href="#safe.methods" title="Safe Methods">Section&nbsp;4.2.1</a>), idempotent (<a href="#idempotent.methods" title="Idempotent Methods">Section&nbsp;4.2.2</a>), cacheable (<a href="#cacheable.methods" title="Cacheable Methods">Section&nbsp;4.2.3</a>), what semantics are to be associated with the payload body if any is present in the request, and what refinements the method
     3458               <p id="rfc.section.8.1.2.p.3">A new method definition needs to indicate whether it is safe (<a href="#safe.methods" title="Safe Methods">Section&nbsp;4.2.1</a>), idempotent (<a href="#idempotent.methods" title="Idempotent Methods">Section&nbsp;4.2.2</a>), cacheable (<a href="#cacheable.methods" title="Cacheable Methods">Section&nbsp;4.2.3</a>), what semantics are to be associated with the payload body if any is present in the request and what refinements the method
    34593459                  makes to header field or status code semantics. If the new method is cacheable, its definition ought to describe how, and
    34603460                  under what conditions, a cache can store a response and use it to satisfy a subsequent request. The new method ought to describe
     
    41874187            <p id="rfc.section.9.4.p.3">Since the <a href="#header.referer" class="smpl">Referer</a> header field tells a target site about the context that resulted in a request, it has the potential to reveal information
    41884188               about the user's immediate browsing history and any personal information that might be found in the referring resource's URI.
    4189                Limitations on Referer are described in <a href="#header.referer" id="rfc.xref.header.referer.3" title="Referer">Section&nbsp;5.5.2</a> to address some of its security considerations.
     4189               Limitations on the Referer header field are described in <a href="#header.referer" id="rfc.xref.header.referer.3" title="Referer">Section&nbsp;5.5.2</a> to address some of its security considerations.
    41904190            </p>
    41914191         </div>
     
    45164516            payload from representations and representations from resources.
    45174517         </p>
    4518          <p id="rfc.section.B.p.2">A new requirement has been added that semantics embedded in a URI should be disabled when those semantics are inconsistent
    4519             with the request method, since this is a common cause of interoperability failure. (<a href="#resources" title="Resources">Section&nbsp;2</a>)
     4518         <p id="rfc.section.B.p.2">A new requirement has been added that semantics embedded in a URI be disabled when those semantics are inconsistent with the
     4519            request method, since this is a common cause of interoperability failure. (<a href="#resources" title="Resources">Section&nbsp;2</a>)
    45204520         </p>
    45214521         <p id="rfc.section.B.p.3">An algorithm has been added for determining if a payload is associated with a specific identifier. (<a href="#identifying.payload" title="Identifying a Representation">Section&nbsp;3.1.4.1</a>)
Note: See TracChangeset for help on using the changeset viewer.