Changeset 1163 for draft-ietf-httpbis/latest/p2-semantics.xml
- Timestamp:
- 11/03/11 06:45:30 (12 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.xml
r1161 r1163 246 246 that defines the protocol referred to as "HTTP/1.1" and, taken together, 247 247 obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages 248 as expressed by request methods, request -header fields, response status codes,249 and response -header fields.248 as expressed by request methods, request header fields, response status codes, 249 and response header fields. 250 250 </t> 251 251 </abstract> … … 282 282 In particular, the sections will be ordered according to the typical 283 283 processing of an HTTP request message (after message parsing): resource 284 mapping, general header fields, methods, request modifiers, response285 status , and resource metadata. The current mess reflects how widely286 dispersed these topics and associated requirements had become in287 <xref target="RFC2616"/>.284 mapping, methods, request modifying header fields, response status, 285 status modifying header fields, and resource metadata. The current mess 286 reflects how widely dispersed these topics and associated requirements 287 had become in <xref target="RFC2616"/>. 288 288 </t> 289 289 … … 530 530 <x:anchor-alias value="request-header"/> 531 531 <t> 532 The request -header fields allow the client to pass additional532 The request header fields allow the client to pass additional 533 533 information about the request, and about the client itself, to the 534 534 server. These fields act as request modifiers, with semantics … … 560 560 <c>User-Agent</c> <c><xref target="header.user-agent"/></c> 561 561 </texttable> 562 <t>563 Request-header field names can be extended reliably only in564 combination with a change in the protocol version. However, new or565 experimental header fields &MAY; be given the semantics of request-header566 fields if all parties in the communication recognize them to567 be request-header fields.568 </t>569 562 </section> 570 563 … … 723 716 <x:anchor-alias value="response-header"/> 724 717 <t> 725 The response -header fields allow the server to pass additional718 The response header fields allow the server to pass additional 726 719 information about the response which cannot be placed in the Status-Line. 727 720 These header fields give information about the server and about … … 729 722 </t> 730 723 <texttable align="left"> 731 <ttcol> Method Name</ttcol><ttcol>Defined in...</ttcol>724 <ttcol>Header Field Name</ttcol><ttcol>Defined in...</ttcol> 732 725 733 726 <c>Accept-Ranges</c> <c>&header-accept-ranges;</c> … … 742 735 <c>WWW-Authenticate</c> <c>&header-www-authenticate;</c> 743 736 </texttable> 744 <t>745 Response-header field names can be extended reliably only in746 combination with a change in the protocol version. However, new or747 experimental header fields &MAY; be given the semantics of response-header748 fields if all parties in the communication recognize them to749 be response-header fields.750 </t>751 737 </section> 752 738 … … 911 897 </t> 912 898 <t> 913 The Max-Forwards request-header field &MAY; be used to target a899 The Max-Forwards header field &MAY; be used to target a 914 900 specific proxy in the request chain (see <xref target="header.max-forwards"/>). 915 901 If no Max-Forwards field is present in the request, then the forwarded … … 1967 1953 </rdf:Description> 1968 1954 <t> 1969 The precondition given in one or more of the request-header fields1955 The precondition given in one or more of the header fields 1970 1956 evaluated to false when it was tested on the server, as defined in 1971 1957 &status-412;. … … 2022 2008 </rdf:Description> 2023 2009 <t> 2024 The request included a Range request-header field (&header-range;) and none of2010 The request included a Range header field (&header-range;) and none of 2025 2011 the range-specifier values in this field overlap the current extent 2026 2012 of the selected resource. See &status-416;. … … 2032 2018 <iref primary="true" item="Status Codes" subitem="417 Expectation Failed" x:for-anchor=""/> 2033 2019 <t> 2034 The expectation given in an Expect request-header field (see <xref target="header.expect"/>)2020 The expectation given in an Expect header field (see <xref target="header.expect"/>) 2035 2021 could not be met by this server, or, if the server is a proxy, 2036 2022 the server has unambiguous evidence that the request could not be met … … 2171 2157 <x:anchor-alias value="Allow-v"/> 2172 2158 <t> 2173 The "Allow" response-header field lists the set of methods advertised as2159 The "Allow" header field lists the set of methods advertised as 2174 2160 supported by the target resource. The purpose of this field is strictly to 2175 2161 inform the recipient of valid request methods associated with the resource. … … 2205 2191 <x:anchor-alias value="expect-params"/> 2206 2192 <t> 2207 The "Expect" request-header field is used to indicate that particular2193 The "Expect" header field is used to indicate that particular 2208 2194 server behaviors are required by the client. 2209 2195 </t> … … 2240 2226 return a 417 (Expectation Failed) status code if it receives a request 2241 2227 with an expectation that it cannot meet. However, the Expect 2242 request-header field itself is end-to-end; it &MUST; be forwarded if the2228 header field itself is end-to-end; it &MUST; be forwarded if the 2243 2229 request is forwarded. 2244 2230 </t> … … 2259 2245 <x:anchor-alias value="mailbox"/> 2260 2246 <t> 2261 The "From" request-header field, if given, &SHOULD; contain an Internet2247 The "From" header field, if given, &SHOULD; contain an Internet 2262 2248 e-mail address for the human user who controls the requesting user 2263 2249 agent. The address &SHOULD; be machine-usable, as defined by "mailbox" … … 2307 2293 <x:anchor-alias value="Location-v"/> 2308 2294 <t> 2309 The "Location" response-header field is used to identify a newly created2295 The "Location" header field is used to identify a newly created 2310 2296 resource, or to redirect the recipient to a different location for 2311 2297 completion of the request. … … 2369 2355 <x:anchor-alias value="Max-Forwards-v"/> 2370 2356 <t> 2371 The "Max-Forwards" request-header field provides a mechanism with the2357 The "Max-Forwards" header field provides a mechanism with the 2372 2358 TRACE (<xref target="TRACE"/>) and OPTIONS (<xref target="OPTIONS"/>) 2373 2359 methods to limit the number of times that the request is forwarded by … … 2404 2390 <x:anchor-alias value="Referer-v"/> 2405 2391 <t> 2406 The "Referer" [sic] request-header field allows the client to specify the2392 The "Referer" [sic] header field allows the client to specify the 2407 2393 URI of the resource from which the effective request URI was obtained (the 2408 2394 "referrer", although the header field is misspelled.). … … 2445 2431 <x:anchor-alias value="Retry-After-v"/> 2446 2432 <t> 2447 The response-header "Retry-After" field can be used with a 503 (Service2433 The header "Retry-After" field can be used with a 503 (Service 2448 2434 Unavailable) response to indicate how long the service is expected to 2449 2435 be unavailable to the requesting client. This field &MAY; also be used … … 2485 2471 <x:anchor-alias value="Server-v"/> 2486 2472 <t> 2487 The "Server" response-header field contains information about the2473 The "Server" header field contains information about the 2488 2474 software used by the origin server to handle the request. 2489 2475 </t> … … 2507 2493 <t> 2508 2494 If the response is being forwarded through a proxy, the proxy 2509 application &MUST-NOT; modify the Server response-header field. Instead, it2495 application &MUST-NOT; modify the Server header field. Instead, it 2510 2496 &MUST; include a Via field (as described in &header-via;). 2511 2497 </t> … … 2527 2513 <x:anchor-alias value="User-Agent-v"/> 2528 2514 <t> 2529 The "User-Agent" request-header field contains information about the user2515 The "User-Agent" header field contains information about the user 2530 2516 agent originating the request. User agents &SHOULD; include this field with 2531 2517 requests.
Note: See TracChangeset
for help on using the changeset viewer.