Changeset 697 for draft-ietf-httpbis/latest/p2-semantics.xml
- Timestamp:
- 25/09/09 14:43:16 (13 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.xml
r695 r697 1868 1868 <x:anchor-alias value="Allow-v"/> 1869 1869 <t> 1870 The response-header field "Allow"lists the set of methods advertised as1871 1872 1873 1874 1870 The "Allow" response-header field lists the set of methods advertised as 1871 supported by the resource identified by the request-target. The purpose of 1872 this field is strictly to inform the recipient of valid methods 1873 associated with the resource. An Allow header field &MUST; be 1874 present in a 405 (Method Not Allowed) response. 1875 1875 </t> 1876 1876 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Allow"/><iref primary="true" item="Grammar" subitem="Allow-v"/> … … 1904 1904 <x:anchor-alias value="expect-params"/> 1905 1905 <t> 1906 The request-header field "Expect"is used to indicate that particular1906 The "Expect" request-header field is used to indicate that particular 1907 1907 server behaviors are required by the client. 1908 1908 </t> … … 1958 1958 <x:anchor-alias value="mailbox"/> 1959 1959 <t> 1960 The request-header field "From", if given, &SHOULD; contain an Internet1960 The "From" request-header field, if given, &SHOULD; contain an Internet 1961 1961 e-mail address for the human user who controls the requesting user 1962 1962 agent. The address &SHOULD; be machine-usable, as defined by "mailbox" … … 2006 2006 <x:anchor-alias value="Location-v"/> 2007 2007 <t> 2008 The response-header field "Location"is used for the identification of a2008 The "Location" response-header field is used for the identification of a 2009 2009 new resource or to redirect the recipient to a location other than the 2010 2010 request-target for completion of the request. For 201 (Created) … … 2048 2048 <x:anchor-alias value="Max-Forwards-v"/> 2049 2049 <t> 2050 The request-header "Max-Forwards"field provides a mechanism with the2050 The "Max-Forwards" request-header field provides a mechanism with the 2051 2051 TRACE (<xref target="TRACE"/>) and OPTIONS (<xref target="OPTIONS"/>) methods to limit the 2052 2052 number of proxies or gateways that can forward the request to the … … 2085 2085 <x:anchor-alias value="Referer-v"/> 2086 2086 <t> 2087 The request-header field "Referer" [sic]allows the client to specify, for2087 The "Referer" [sic] request-header field allows the client to specify, for 2088 2088 the server's benefit, the address (URI) of the resource from which the 2089 2089 request-target was obtained (the "referrer", although the header field is … … 2165 2165 <x:anchor-alias value="Server-v"/> 2166 2166 <t> 2167 The response-header field "Server"contains information about the2167 The "Server" response-header field contains information about the 2168 2168 software used by the origin server to handle the request. The field 2169 2169 can contain multiple product tokens (&product-tokens;) and comments … … 2205 2205 <x:anchor-alias value="User-Agent-v"/> 2206 2206 <t> 2207 The request-header field "User-Agent"contains information about the2207 The "User-Agent" request-header field contains information about the 2208 2208 user agent originating the request. This is for statistical purposes, 2209 2209 the tracing of protocol violations, and automated recognition of user
Note: See TracChangeset
for help on using the changeset viewer.