Ignore:
Timestamp:
11/03/11 05:42:12 (10 years ago)
Author:
fielding@…
Message:

update generated HTML

File:
1 edited

Legend:

Unmodified
Added
Removed

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

    r1160 r1162  
    774774             &lt;WWW-Authenticate, defined in <a href="#Part7" id="rfc.xref.Part7.4"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.www-authenticate" title="WWW-Authenticate">Section 4.4</a>&gt;
    775775</pre><h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a id="method" href="#method">Method</a></h1>
    776       <p id="rfc.section.2.p.1">The Method token indicates the method to be performed on the target resource (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.17"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). The method is case-sensitive.
     776      <p id="rfc.section.2.p.1">The Method token indicates the request method to be performed on the target resource (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.17"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). The method is case-sensitive.
    777777      </p>
    778778      <div id="rfc.figure.u.8"></div><pre class="inline"><span id="rfc.iref.g.1"></span>  <a href="#method" class="smpl">Method</a>         = <a href="#core.rules" class="smpl">token</a>
    … …  
    829829         </table>
    830830      </div>
    831       <p id="rfc.section.2.1.p.2">Note that this list is not exhaustive — it does not include methods defined in other specifications.</p>
     831      <p id="rfc.section.2.1.p.2">Note that this list is not exhaustive — it does not include request methods defined in other specifications.</p>
    832832      <h2 id="rfc.section.2.2"><a href="#rfc.section.2.2">2.2</a>&nbsp;<a id="method.registry" href="#method.registry">Method Registry</a></h2>
    833833      <p id="rfc.section.2.2.p.1">The HTTP Method Registry defines the name space for the Method token in the Request line of an HTTP request.</p>
    … …  
    13091309      </p>
    13101310      <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a id="method.definitions" href="#method.definitions">Method Definitions</a></h1>
    1311       <p id="rfc.section.7.p.1">The set of common methods for HTTP/1.1 is defined below. Although this set can be expanded, additional methods cannot be assumed
    1312          to share the same semantics for separately extended clients and servers.
     1311      <p id="rfc.section.7.p.1">The set of common request methods for HTTP/1.1 is defined below. Although this set can be expanded, additional methods cannot
     1312         be assumed to share the same semantics for separately extended clients and servers.
    13131313      </p>
    13141314      <h2 id="rfc.section.7.1"><a href="#rfc.section.7.1">7.1</a>&nbsp;<a id="safe.and.idempotent" href="#safe.and.idempotent">Safe and Idempotent Methods</a></h2>
    … …  
    13181318         the user to be aware of any actions they take which might have an unexpected significance to themselves or others.
    13191319      </p>
    1320       <p id="rfc.section.7.1.1.p.2">In particular, the convention has been established that the GET, HEAD, OPTIONS, and TRACE methods <em class="bcp14">SHOULD NOT</em> have the significance of taking an action other than retrieval. These methods ought to be considered "<dfn id="safe">safe</dfn>". This allows user agents to represent other methods, such as POST, PUT and DELETE, in a special way, so that the user is
     1320      <p id="rfc.section.7.1.1.p.2">In particular, the convention has been established that the GET, HEAD, OPTIONS, and TRACE request methods <em class="bcp14">SHOULD NOT</em> have the significance of taking an action other than retrieval. These request methods ought to be considered "<dfn id="safe">safe</dfn>". This allows user agents to represent other methods, such as POST, PUT and DELETE, in a special way, so that the user is
    13211321         made aware of the fact that a possibly unsafe action is being requested.
    13221322      </p>
    … …  
    13271327      <div id="rfc.iref.i.1"></div>
    13281328      <h3 id="rfc.section.7.1.2"><a href="#rfc.section.7.1.2">7.1.2</a>&nbsp;<a id="idempotent.methods" href="#idempotent.methods">Idempotent Methods</a></h3>
    1329       <p id="rfc.section.7.1.2.p.1">Methods can also have the property of "idempotence" in that, aside from error or expiration issues, the intended effect of
    1330          multiple identical requests is the same as for a single request. The methods PUT, DELETE, and all safe methods are idempotent.
     1329      <p id="rfc.section.7.1.2.p.1">Request methods can also have the property of "idempotence" in that, aside from error or expiration issues, the intended effect
     1330         of multiple identical requests is the same as for a single request. PUT, DELETE, and all safe request methods are idempotent.
    13311331         It is important to note that idempotence refers only to changes requested by the client: a server is free to change its state
    13321332         due to multiple requests for the purpose of tracking those requests, versioning of results, etc.
    … …  
    13351335      <div id="rfc.iref.o.1"></div>
    13361336      <div id="rfc.iref.m.1"></div>
    1337       <p id="rfc.section.7.2.p.1">The OPTIONS method represents a request for information about the communication options available on the request/response
    1338          chain identified by the effective request URI. This method allows the client to determine the options and/or requirements
    1339          associated with a resource, or the capabilities of a server, without implying a resource action or initiating a resource retrieval.
    1340       </p>
    1341       <p id="rfc.section.7.2.p.2">Responses to this method are not cacheable.</p>
     1337      <p id="rfc.section.7.2.p.1">The OPTIONS method requests information about the communication options available on the request/response chain identified
     1338         by the effective request URI. This method allows a client to determine the options and/or requirements associated with a resource,
     1339         or the capabilities of a server, without implying a resource action or initiating a resource retrieval.
     1340      </p>
     1341      <p id="rfc.section.7.2.p.2">Responses to the OPTIONS method are not cacheable.</p>
    13421342      <p id="rfc.section.7.2.p.3">If the OPTIONS request includes a message-body (as indicated by the presence of Content-Length or Transfer-Encoding), then
    13431343         the media type <em class="bcp14">MUST</em> be indicated by a Content-Type field. Although this specification does not define any use for such a body, future extensions
    … …  
    13611361      <div id="rfc.iref.g.5"></div>
    13621362      <div id="rfc.iref.m.2"></div>
    1363       <p id="rfc.section.7.3.p.1">The GET method means retrieve whatever information (in the form of a representation) currently corresponds to the target resource.</p>
     1363      <p id="rfc.section.7.3.p.1">The GET method requests transfer of a current representation of the target resource.</p>
    13641364      <p id="rfc.section.7.3.p.2">If the target resource is a data-producing process, it is the produced data which shall be returned as the representation
    13651365         in the response and not the source text of the process, unless that text happens to be the output of the process.
    13661366      </p>
    13671367      <p id="rfc.section.7.3.p.3">The semantics of the GET method change to a "conditional GET" if the request message includes an If-Modified-Since, If-Unmodified-Since,
    1368          If-Match, If-None-Match, or If-Range header field. A conditional GET method requests that the representation be transferred
    1369          only under the circumstances described by the conditional header field(s). The conditional GET method is intended to reduce
    1370          unnecessary network usage by allowing cached representations to be refreshed without requiring multiple requests or transferring
    1371          data already held by the client.
     1368         If-Match, If-None-Match, or If-Range header field. A conditional GET requests that the representation be transferred only
     1369         under the circumstances described by the conditional header field(s). The conditional GET request is intended to reduce unnecessary
     1370         network usage by allowing cached representations to be refreshed without requiring multiple requests or transferring data
     1371         already held by the client.
    13721372      </p>
    13731373      <p id="rfc.section.7.3.p.4">The semantics of the GET method change to a "partial GET" if the request message includes a Range header field. A partial
    1374          GET requests that only part of the representation be transferred, as described in <a href="p5-range.html#header.range" title="Range">Section 5.4</a> of <a href="#Part5" id="rfc.xref.Part5.10"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>. The partial GET method is intended to reduce unnecessary network usage by allowing partially-retrieved representations to
    1375          be completed without transferring data already held by the client.
     1374         GET requests that only part of the representation be transferred, as described in <a href="p5-range.html#header.range" title="Range">Section 5.4</a> of <a href="#Part5" id="rfc.xref.Part5.10"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>. The partial GET request is intended to reduce unnecessary network usage by allowing partially-retrieved representations
     1375         to be completed without transferring data already held by the client.
    13761376      </p>
    13771377      <p id="rfc.section.7.3.p.5">The response to a GET request is cacheable and <em class="bcp14">MAY</em> be used to satisfy subsequent GET and HEAD requests (see <a href="#Part6" id="rfc.xref.Part6.8"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).
    … …  
    13931393      <div id="rfc.iref.m.4"></div>
    13941394      <h2 id="rfc.section.7.5"><a href="#rfc.section.7.5">7.5</a>&nbsp;<a id="POST" href="#POST">POST</a></h2>
    1395       <p id="rfc.section.7.5.p.1">The POST method is used to request that the origin server accept the representation enclosed in the request as data to be
    1396          processed by the target resource. POST is designed to allow a uniform method to cover the following functions:
     1395      <p id="rfc.section.7.5.p.1">The POST method requests that the origin server accept the representation enclosed in the request as data to be processed
     1396         by the target resource. POST is designed to allow a uniform method to cover the following functions:
    13971397      </p>
    13981398      <ul>
    … …  
    14201420      <div id="rfc.iref.m.5"></div>
    14211421      <h2 id="rfc.section.7.6"><a href="#rfc.section.7.6">7.6</a>&nbsp;<a id="PUT" href="#PUT">PUT</a></h2>
    1422       <p id="rfc.section.7.6.p.1">The PUT method is used to request that the state of the target resource be created or replaced with the state defined by the
    1423          representation enclosed in the request message payload. A successful PUT of a given representation would suggest that a subsequent
    1424          GET on that same target resource will result in an equivalent representation being returned in a 200 (OK) response. However,
    1425          there is no guarantee that such a state change will be observable, since the target resource might be acted upon by other
    1426          user agents in parallel, or might be subject to dynamic processing by the origin server, before any subsequent GET is received.
    1427          A successful response only implies that the user agent's intent was achieved at the time of its processing by the origin server.
     1422      <p id="rfc.section.7.6.p.1">The PUT method requests that the state of the target resource be created or replaced with the state defined by the representation
     1423         enclosed in the request message payload. A successful PUT of a given representation would suggest that a subsequent GET on
     1424         that same target resource will result in an equivalent representation being returned in a 200 (OK) response. However, there
     1425         is no guarantee that such a state change will be observable, since the target resource might be acted upon by other user agents
     1426         in parallel, or might be subject to dynamic processing by the origin server, before any subsequent GET is received. A successful
     1427         response only implies that the user agent's intent was achieved at the time of its processing by the origin server.
    14281428      </p>
    14291429      <p id="rfc.section.7.6.p.2">If the target resource does not have a current representation and the PUT successfully creates one, then the origin server <em class="bcp14">MUST</em> inform the user agent by sending a 201 (Created) response. If the target resource does have a current representation and that
    … …  
    14941494      <div id="rfc.iref.t.1"></div>
    14951495      <div id="rfc.iref.m.7"></div>
    1496       <p id="rfc.section.7.8.p.1">The TRACE method is used to invoke a remote, application-layer loop-back of the request message. The final recipient of the
    1497          request <em class="bcp14">SHOULD</em> reflect the message received back to the client as the message-body of a 200 (OK) response. The final recipient is either
     1496      <p id="rfc.section.7.8.p.1">The TRACE method requests a remote, application-layer loop-back of the request message. The final recipient of the request <em class="bcp14">SHOULD</em> reflect the message received back to the client as the message-body of a 200 (OK) response. The final recipient is either
    14981497         the origin server or the first proxy or gateway to receive a Max-Forwards value of zero (0) in the request (see <a href="#header.max-forwards" id="rfc.xref.header.max-forwards.3" title="Max-Forwards">Section&nbsp;9.5</a>). A TRACE request <em class="bcp14">MUST NOT</em> include a message-body.
    14991498      </p>
    … …  
    15081507      <div id="rfc.iref.m.8"></div>
    15091508      <h2 id="rfc.section.7.9"><a href="#rfc.section.7.9">7.9</a>&nbsp;<a id="CONNECT" href="#CONNECT">CONNECT</a></h2>
    1510       <p id="rfc.section.7.9.p.1">The CONNECT method is used with a proxy to dynamically switch the connection to a tunnel.</p>
    1511       <p id="rfc.section.7.9.p.2">When using CONNECT, the request-target <em class="bcp14">MUST</em> be use the authority form (<a href="p1-messaging.html#request-target" title="request-target">Section 4.1.2</a> of <a href="#Part1" id="rfc.xref.Part1.26"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>); i.e., the host name and port number destination of the requested connection separated by a colon:
     1509      <p id="rfc.section.7.9.p.1">The CONNECT method requests that the proxy establish a tunnel to the request-target and then restrict its behavior to blind
     1510         forwarding of packets until the connection is closed.
     1511      </p>
     1512      <p id="rfc.section.7.9.p.2">When using CONNECT, the request-target <em class="bcp14">MUST</em> use the authority form (<a href="p1-messaging.html#request-target" title="request-target">Section 4.1.2</a> of <a href="#Part1" id="rfc.xref.Part1.26"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>); i.e., the request-target consists of only the host name and port number of the tunnel destination, separated by a colon.
     1513         For example,
    15121514      </p>
    15131515      <div id="rfc.figure.u.10"></div><pre class="text2">CONNECT server.example.com:80 HTTP/1.1
    … …  
    18901892      <div id="rfc.iref.s.34"></div>
    18911893      <h3 id="rfc.section.8.4.16"><a href="#rfc.section.8.4.16">8.4.16</a>&nbsp;<a id="status.415" href="#status.415">415 Unsupported Media Type</a></h3>
    1892       <p id="rfc.section.8.4.16.p.1">The server is refusing to service the request because the representation of the request is in a format not supported by the
    1893          target resource for the requested method.
     1894      <p id="rfc.section.8.4.16.p.1">The server is refusing to service the request because the request payload is in a format not supported by this request method
     1895         on the target resource.
    18941896      </p>
    18951897      <div id="rfc.iref.55"></div>
    … …  
    19721974      <h2 id="rfc.section.9.1"><a href="#rfc.section.9.1">9.1</a>&nbsp;<a id="header.allow" href="#header.allow">Allow</a></h2>
    19731975      <p id="rfc.section.9.1.p.1">The "Allow" response-header field lists the set of methods advertised as supported by the target resource. The purpose of
    1974          this field is strictly to inform the recipient of valid methods associated with the resource.
     1976         this field is strictly to inform the recipient of valid request methods associated with the resource.
    19751977      </p>
    19761978      <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.6"></span><span id="rfc.iref.g.7"></span>  <a href="#header.allow" class="smpl">Allow</a>   = "Allow" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.allow" class="smpl">Allow-v</a>
    … …  
    20732075      <p id="rfc.section.9.5.p.4">Each proxy or gateway recipient of a TRACE or OPTIONS request containing a Max-Forwards header field <em class="bcp14">MUST</em> check and update its value prior to forwarding the request. If the received value is zero (0), the recipient <em class="bcp14">MUST NOT</em> forward the request; instead, it <em class="bcp14">MUST</em> respond as the final recipient. If the received Max-Forwards value is greater than zero, then the forwarded message <em class="bcp14">MUST</em> contain an updated Max-Forwards field with a value decremented by one (1).
    20742076      </p>
    2075       <p id="rfc.section.9.5.p.5">The Max-Forwards header field <em class="bcp14">MAY</em> be ignored for all other methods.
     2077      <p id="rfc.section.9.5.p.5">The Max-Forwards header field <em class="bcp14">MAY</em> be ignored for all other request methods.
    20762078      </p>
    20772079      <div id="rfc.iref.r.1"></div>
    … …  
    21582160</pre><h1 id="rfc.section.10"><a href="#rfc.section.10">10.</a>&nbsp;<a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1>
    21592161      <h2 id="rfc.section.10.1"><a href="#rfc.section.10.1">10.1</a>&nbsp;<a id="method.registration" href="#method.registration">Method Registry</a></h2>
    2160       <p id="rfc.section.10.1.p.1">The registration procedure for HTTP Methods is defined by <a href="#method.registry" title="Method Registry">Section&nbsp;2.2</a> of this document.
     2162      <p id="rfc.section.10.1.p.1">The registration procedure for HTTP request methods is defined by <a href="#method.registry" title="Method Registry">Section&nbsp;2.2</a> of this document.
    21612163      </p>
    21622164      <p id="rfc.section.10.1.p.2">The HTTP Method Registry shall be created at &lt;<a href="http://www.iana.org/assignments/http-methods">http://www.iana.org/assignments/http-methods</a>&gt; and be populated with the registrations below:
    … …  
    25822584         to uniquely identify the user.
    25832585      </p>
    2584       <p id="rfc.section.11.1.p.9">Some methods, like TRACE (<a href="#TRACE" id="rfc.xref.TRACE.4" title="TRACE">Section&nbsp;7.8</a>), expose information that was sent in request header fields within the body of their response. Clients <em class="bcp14">SHOULD</em> be careful with sensitive information, like Cookies, Authorization credentials and other header fields that might be used
     2586      <p id="rfc.section.11.1.p.9">Some request methods, like TRACE (<a href="#TRACE" id="rfc.xref.TRACE.4" title="TRACE">Section&nbsp;7.8</a>), expose information that was sent in request header fields within the body of their response. Clients <em class="bcp14">SHOULD</em> be careful with sensitive information, like Cookies, Authorization credentials, and other header fields that might be used
    25852587         to collect data from the client.
    25862588      </p>
Note: See TracChangeset for help on using the changeset viewer.