Changeset 1851 for draft-ietf-httpbis/latest/p2-semantics.xml
- Timestamp:
- 02/09/12 06:46:39 (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.xml
r1850 r1851 224 224 intentions defined by each request method (<xref target="methods"/>), 225 225 extensions to those semantics that might be described in request header 226 fields (<xref target="request. fields"/>),226 fields (<xref target="request.header.fields"/>), 227 227 the meaning of status codes to indicate a machine-readable response 228 228 (<xref target="status.codes"/>), and other control data 229 and resource metadata that might be given in response header fields. 229 and resource metadata that might be given in response header fields 230 (<xref target="response.header.fields"/>). 230 231 </t> 231 232 <t><iref item="content negotiation"/> … … 280 281 request semantics, which is made possible by vesting the request 281 282 semantics in the request method (<xref target="methods"/>) and a few 282 request-modifying header fields (<xref target="request. fields"/>).283 request-modifying header fields (<xref target="request.header.fields"/>). 283 284 Resource owners &SHOULD-NOT; include request semantics within a URI, 284 285 such as by specifying an action to invoke within the path or query … … 471 472 and what is expected by the client as a successful result. The request 472 473 semantics &MAY; be further specialized by the semantics of some header 473 fields when present in a request (<xref target="request. fields"/>) if474 those additional semantics do not conflict with the method.474 fields when present in a request (<xref target="request.header.fields"/>) 475 if those additional semantics do not conflict with the method. 475 476 </t> 476 477 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="method"/> … … 1131 1132 </section> 1132 1133 1133 <section title="Header Fields" anchor="header.fields">1134 1135 <section title="Request-modifier Header Fields" anchor="request.fields">1136 </section>1137 1138 <section title="Status-modifier Header Fields" anchor="response.fields">1139 </section>1140 1141 <section title="Resource Metadata Fields" anchor="resource.fields">1142 </section>1143 1144 <section title="Payload Metadata Fields" anchor="payload.fields">1145 </section>1146 1147 1134 <section title="Request Header Fields" anchor="request.header.fields"> 1148 1135 <x:anchor-alias value="request-header"/> … … 1178 1165 <c>User-Agent</c> <c><xref target="header.user-agent"/></c> 1179 1166 </texttable> 1180 </section> 1181 1182 <section title="Response Header Fields" anchor="response.header.fields"> 1183 <x:anchor-alias value="response-header"/> 1184 <t> 1185 The response header fields allow the server to pass additional 1186 information about the response which cannot be placed in the status-line. 1187 These header fields give information about the server and about 1188 further access to the target resource (&effective-request-uri;). 1189 </t> 1190 <texttable align="left"> 1191 <ttcol>Header Field Name</ttcol><ttcol>Defined in...</ttcol> 1192 1193 <c>Accept-Ranges</c> <c>&header-accept-ranges;</c> 1194 <c>Age</c> <c>&header-age;</c> 1195 <c>Allow</c> <c><xref target="header.allow"/></c> 1196 <c>Date</c> <c><xref target="header.date"/></c> 1197 <c>ETag</c> <c>&header-etag;</c> 1198 <c>Location</c> <c><xref target="header.location"/></c> 1199 <c>Proxy-Authenticate</c> <c>&header-proxy-authenticate;</c> 1200 <c>Retry-After</c> <c><xref target="header.retry-after"/></c> 1201 <c>Server</c> <c><xref target="header.server"/></c> 1202 <c>Vary</c> <c>&header-vary;</c> 1203 <c>WWW-Authenticate</c> <c>&header-www-authenticate;</c> 1204 </texttable> 1205 </section> 1206 1167 1168 <section title="Controls" anchor="request.controls"> 1169 </section> 1170 1171 <section title="Conditionals" anchor="request.conditionals"> 1172 </section> 1173 1174 <section title="Content Negotiation" anchor="request.conneg"> 1175 </section> 1176 1177 <section title="Information" anchor="request.inform"> 1178 </section> 1207 1179 </section> 1208 1180 … … 2207 2179 </section> 2208 2180 </section> 2181 </section> 2182 2183 <section title="Response Header Fields" anchor="response.header.fields"> 2184 <x:anchor-alias value="response-header"/> 2185 <t> 2186 The response header fields allow the server to pass additional 2187 information about the response which cannot be placed in the status-line. 2188 These header fields give information about the server and about 2189 further access to the target resource (&effective-request-uri;). 2190 </t> 2191 <texttable align="left"> 2192 <ttcol>Header Field Name</ttcol><ttcol>Defined in...</ttcol> 2193 2194 <c>Accept-Ranges</c> <c>&header-accept-ranges;</c> 2195 <c>Age</c> <c>&header-age;</c> 2196 <c>Allow</c> <c><xref target="header.allow"/></c> 2197 <c>Date</c> <c><xref target="header.date"/></c> 2198 <c>ETag</c> <c>&header-etag;</c> 2199 <c>Location</c> <c><xref target="header.location"/></c> 2200 <c>Proxy-Authenticate</c> <c>&header-proxy-authenticate;</c> 2201 <c>Retry-After</c> <c><xref target="header.retry-after"/></c> 2202 <c>Server</c> <c><xref target="header.server"/></c> 2203 <c>Vary</c> <c>&header-vary;</c> 2204 <c>WWW-Authenticate</c> <c>&header-www-authenticate;</c> 2205 </texttable> 2209 2206 </section> 2210 2207
Note: See TracChangeset
for help on using the changeset viewer.