Changeset 1557 for draft-ietf-httpbis/latest/p2-semantics.xml
- Timestamp:
- 03/03/12 23:56:54 (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.xml
r1554 r1557 401 401 402 402 <section title="Method" anchor="method"> 403 <x:anchor-alias value=" Method"/>403 <x:anchor-alias value="method"/> 404 404 <x:anchor-alias value="extension-method"/> 405 405 <t> 406 The Method token indicates the request method to be performed on the target406 The method token indicates the request method to be performed on the target 407 407 resource (&effective-request-uri;). The method is case-sensitive. 408 408 </t> 409 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem=" Method"/>410 <x:ref> Method</x:ref> = <x:ref>token</x:ref>409 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="method"/> 410 <x:ref>method</x:ref> = <x:ref>token</x:ref> 411 411 </artwork></figure> 412 412 <t> … … 449 449 <section title="Method Registry" anchor="method.registry"> 450 450 <t> 451 The HTTP Method Registry defines the name space for the Method token in the451 The HTTP Method Registry defines the name space for the method token in the 452 452 Request line of an HTTP request. 453 453 </t> … … 630 630 <t> 631 631 The response header fields allow the server to pass additional 632 information about the response which cannot be placed in the Status-Line.632 information about the response which cannot be placed in the status-line. 633 633 These header fields give information about the server and about 634 634 further access to the target resource (&effective-request-uri;). … … 654 654 655 655 <section title="Status Code and Reason Phrase" anchor="status.code.and.reason.phrase"> 656 <x:anchor-alias value=" Reason-Phrase"/>657 <x:anchor-alias value=" Status-Code"/>656 <x:anchor-alias value="reason-phrase"/> 657 <x:anchor-alias value="status-code"/> 658 658 <x:anchor-alias value="extension-code"/> 659 659 <t> 660 The Status-Code element is a 3-digit integer result code of the attempt to660 The status-code element is a 3-digit integer result code of the attempt to 661 661 understand and satisfy the request. 662 662 </t> 663 663 <t> 664 The Reason-Phrase is intended to give a short textual description of the665 Status-Code and is intended for a human user. The client does not need666 to examine or display the Reason-Phrase.667 </t> 668 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem=" Status-Code"/><iref primary="true" item="Grammar" subitem="extension-code"/><iref primary="true" item="Grammar" subitem="Reason-Phrase"/>669 <x:ref> Status-Code</x:ref> = 3<x:ref>DIGIT</x:ref>670 <x:ref> Reason-Phrase</x:ref> = *( <x:ref>HTAB</x:ref> / <x:ref>SP</x:ref> / <x:ref>VCHAR</x:ref> / <x:ref>obs-text</x:ref> )664 The reason-phrase is intended to give a short textual description of the 665 status-code and is intended for a human user. The client does not need 666 to examine or display the reason-phrase. 667 </t> 668 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="status-code"/><iref primary="true" item="Grammar" subitem="extension-code"/><iref primary="true" item="Grammar" subitem="reason-phrase"/> 669 <x:ref>status-code</x:ref> = 3<x:ref>DIGIT</x:ref> 670 <x:ref>reason-phrase</x:ref> = *( <x:ref>HTAB</x:ref> / <x:ref>SP</x:ref> / <x:ref>VCHAR</x:ref> / <x:ref>obs-text</x:ref> ) 671 671 </artwork></figure> 672 672 <t> … … 694 694 </t> 695 695 <texttable align="left"> 696 <ttcol> Status-Code</ttcol>697 <ttcol> Reason-Phrase</ttcol>696 <ttcol>status-code</ttcol> 697 <ttcol>reason-phrase</ttcol> 698 698 <ttcol>Defined in...</ttcol> 699 699 … … 752 752 <section title="Status Code Registry" anchor="status.code.registry"> 753 753 <t> 754 The HTTP Status Code Registry defines the name space for the Status-Code755 token in the Status-Line of an HTTP response.754 The HTTP Status Code Registry defines the name space for the status-code 755 token in the status-line of an HTTP response. 756 756 </t> 757 757 <t> … … 917 917 </rdf:Description> 918 918 <iref primary="true" item="OPTIONS method" x:for-anchor=""/> 919 <iref primary="true" item=" Methods" subitem="OPTIONS" x:for-anchor=""/>919 <iref primary="true" item="methods" subitem="OPTIONS" x:for-anchor=""/> 920 920 <t> 921 921 The OPTIONS method requests information about the … … 976 976 </rdf:Description> 977 977 <iref primary="true" item="GET method" x:for-anchor=""/> 978 <iref primary="true" item=" Methods" subitem="GET" x:for-anchor=""/>978 <iref primary="true" item="methods" subitem="GET" x:for-anchor=""/> 979 979 <t> 980 980 The GET method requests transfer of a current representation of … … 1024 1024 </rdf:Description> 1025 1025 <iref primary="true" item="HEAD method" x:for-anchor=""/> 1026 <iref primary="true" item=" Methods" subitem="HEAD" x:for-anchor=""/>1026 <iref primary="true" item="methods" subitem="HEAD" x:for-anchor=""/> 1027 1027 <t> 1028 1028 The HEAD method is identical to GET except that the server &MUST-NOT; … … 1049 1049 <section title="POST" anchor="POST"> 1050 1050 <iref primary="true" item="POST method" x:for-anchor=""/> 1051 <iref primary="true" item=" Methods" subitem="POST" x:for-anchor=""/>1051 <iref primary="true" item="methods" subitem="POST" x:for-anchor=""/> 1052 1052 <t> 1053 1053 The POST method requests that the origin server accept the … … 1105 1105 <section title="PUT" anchor="PUT"> 1106 1106 <iref primary="true" item="PUT method" x:for-anchor=""/> 1107 <iref primary="true" item=" Methods" subitem="PUT" x:for-anchor=""/>1107 <iref primary="true" item="methods" subitem="PUT" x:for-anchor=""/> 1108 1108 <t> 1109 1109 The PUT method requests that the state of the target resource … … 1227 1227 <section title="DELETE" anchor="DELETE"> 1228 1228 <iref primary="true" item="DELETE method" x:for-anchor=""/> 1229 <iref primary="true" item=" Methods" subitem="DELETE" x:for-anchor=""/>1229 <iref primary="true" item="methods" subitem="DELETE" x:for-anchor=""/> 1230 1230 <t> 1231 1231 The DELETE method requests that the origin server delete the target … … 1263 1263 </rdf:Description> 1264 1264 <iref primary="true" item="TRACE method" x:for-anchor=""/> 1265 <iref primary="true" item=" Methods" subitem="TRACE" x:for-anchor=""/>1265 <iref primary="true" item="methods" subitem="TRACE" x:for-anchor=""/> 1266 1266 <t> 1267 1267 The TRACE method requests a remote, application-layer loop-back … … 1292 1292 <section title="CONNECT" anchor="CONNECT"> 1293 1293 <iref primary="true" item="CONNECT method" x:for-anchor=""/> 1294 <iref primary="true" item=" Methods" subitem="CONNECT" x:for-anchor=""/>1294 <iref primary="true" item="methods" subitem="CONNECT" x:for-anchor=""/> 1295 1295 <t> 1296 1296 The CONNECT method requests that the proxy establish a tunnel … … 1372 1372 <section title="Status Code Definitions" anchor="status.codes"> 1373 1373 <t> 1374 The first digit of the Status-Code defines the class of response. The1374 The first digit of the status-code defines the class of response. The 1375 1375 last two digits do not have any categorization role. There are 5 1376 1376 values for the first digit: … … 1398 1398 </t> 1399 1399 <t> 1400 Each Status-Code is described below, including any metadata required1400 Each status-code is described below, including any metadata required 1401 1401 in the response. 1402 1402 </t> … … 1410 1410 <t> 1411 1411 This class of status code indicates a provisional response, 1412 consisting only of the Status-Line and optional header fields, and is1412 consisting only of the status-line and optional header fields, and is 1413 1413 terminated by an empty line. There are no required header fields for this 1414 1414 class of status code. Since HTTP/1.0 did not define any 1xx status … … 1937 1937 <iref primary="true" item="Status Codes" subitem="405 Method Not Allowed" x:for-anchor=""/> 1938 1938 <t> 1939 The method specified in the Request-Line is not allowed for the target1939 The method specified in the request-line is not allowed for the target 1940 1940 resource. The response &MUST; include an Allow header field containing a 1941 1941 list of valid methods for the requested resource. … … 2425 2425 </t> 2426 2426 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Allow"/> 2427 <x:ref>Allow</x:ref> = #<x:ref> Method</x:ref>2427 <x:ref>Allow</x:ref> = #<x:ref>method</x:ref> 2428 2428 </artwork></figure> 2429 2429 <t> … … 3986 3986 <figure> 3987 3987 <artwork type="abnf" name="p2-semantics.parsed-abnf"> 3988 <x:ref>Allow</x:ref> = [ ( "," / Method ) *( OWS "," [ OWS Method ] ) ]3988 <x:ref>Allow</x:ref> = [ ( "," / method ) *( OWS "," [ OWS method ] ) ] 3989 3989 3990 3990 <x:ref>BWS</x:ref> = <BWS, defined in [Part1], Section 3.2.1> … … 4003 4003 4004 4004 <x:ref>Max-Forwards</x:ref> = 1*DIGIT 4005 <x:ref>Method</x:ref> = token4006 4005 4007 4006 <x:ref>OWS</x:ref> = <OWS, defined in [Part1], Section 3.2.1> 4008 4007 4009 4008 <x:ref>RWS</x:ref> = <RWS, defined in [Part1], Section 3.2.1> 4010 <x:ref>Reason-Phrase</x:ref> = *( HTAB / SP / VCHAR / obs-text )4011 4009 <x:ref>Referer</x:ref> = absolute-URI / partial-URI 4012 4010 <x:ref>Retry-After</x:ref> = HTTP-date / delta-seconds 4013 4011 4014 4012 <x:ref>Server</x:ref> = product *( RWS ( product / comment ) ) 4015 <x:ref>Status-Code</x:ref> = 3DIGIT4016 4013 4017 4014 <x:ref>URI-reference</x:ref> = <URI-reference, defined in [Part1], Section 2.7> … … 4052 4049 4053 4050 <x:ref>mailbox</x:ref> = <mailbox, defined in [RFC5322], Section 3.4> 4051 <x:ref>method</x:ref> = token 4054 4052 <x:ref>minute</x:ref> = 2DIGIT 4055 4053 <x:ref>month</x:ref> = %x4A.61.6E ; Jan … … 4075 4073 <x:ref>quoted-string</x:ref> = <quoted-string, defined in [Part1], Section 3.2.4> 4076 4074 4075 <x:ref>reason-phrase</x:ref> = *( HTAB / SP / VCHAR / obs-text ) 4077 4076 <x:ref>rfc1123-date</x:ref> = day-name "," SP date1 SP time-of-day SP GMT 4078 4077 <x:ref>rfc850-date</x:ref> = day-name-l "," SP date2 SP time-of-day SP GMT 4079 4078 4080 4079 <x:ref>second</x:ref> = 2DIGIT 4080 <x:ref>status-code</x:ref> = 3DIGIT 4081 4081 4082 4082 <x:ref>time-of-day</x:ref> = hour ":" minute ":" second … … 4093 4093 ; Location defined but not used 4094 4094 ; Max-Forwards defined but not used 4095 ; Reason-Phrase defined but not used4096 4095 ; Referer defined but not used 4097 4096 ; Retry-After defined but not used 4098 4097 ; Server defined but not used 4099 ; Status-Code defined but not used4100 4098 ; User-Agent defined but not used 4099 ; reason-phrase defined but not used 4100 ; status-code defined but not used 4101 4101 </artwork></figure></section> 4102 4102 <?ENDINC p2-semantics.abnf-appendix ?> … … 4313 4313 <t> 4314 4314 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/94"/>: 4315 " Reason-Phrase BNF"4315 "reason-phrase BNF" 4316 4316 </t> 4317 4317 </list> … … 4522 4522 <t> 4523 4523 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/137"/>: 4524 "duplicate ABNF for Reason-Phrase"4524 "duplicate ABNF for reason-phrase" 4525 4525 </t> 4526 4526 <t>
Note: See TracChangeset
for help on using the changeset viewer.