Changeset 1750 for draft-ietf-httpbis/latest/p1-messaging.xml
- Timestamp:
- 09/07/12 19:06:58 (9 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.xml
r1747 r1750 1103 1103 <x:anchor-alias value="response"/> 1104 1104 <x:anchor-alias value="status-line"/> 1105 <x:anchor-alias value="status-code"/> 1106 <x:anchor-alias value="reason-phrase"/> 1105 1107 <t> 1106 1108 The first line of a response message is the status-line, consisting … … 1116 1118 with a status-line and matches the ABNF rule for HTTP-message. 1117 1119 </t> 1118 1119 <t anchor="status-code"> 1120 The status-code element is a 3-digit integer result code of the attempt to 1121 understand and satisfy the request. See &status-codes; for 1122 further information, such as the list of status codes defined by this 1123 specification, the IANA registry, and considerations for new status codes. 1120 <t> 1121 The status-code element is a 3-digit integer code describing the 1122 result of the server's attempt to understand and satisfy the client's 1123 corresponding request. The rest of the response message is to be 1124 interpreted in light of the semantics defined for that status code. 1125 See &status-codes; for information about the semantics of status codes, 1126 including the classes of status code (indicated by the first digit), 1127 the status codes defined by this specification, considerations for the 1128 definition of new status codes, and the IANA registry. 1124 1129 </t> 1125 1130 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="status-code"/> 1126 1131 <x:ref>status-code</x:ref> = 3<x:ref>DIGIT</x:ref> 1127 1132 </artwork></figure> 1128 1129 <t anchor="reason-phrase"> 1133 <t> 1130 1134 The reason-phrase element exists for the sole purpose of providing a 1131 1135 textual description associated with the numeric status code, mostly … … 1498 1502 The presence of a message body in a response depends on both 1499 1503 the request method to which it is responding and the response 1500 status code (<xref target="status -code"/>).1504 status code (<xref target="status.line"/>). 1501 1505 Responses to the HEAD request method never include a message body 1502 1506 because the associated response header fields (e.g., … … 1508 1512 <x:ref>304 (Not Modified)</x:ref> responses &MUST-NOT; include a message body. 1509 1513 All other responses do include a message body, although the body 1510 &MAY; be of zero length. (See &status-codes; and &status-304;.)1514 &MAY; be of zero length. 1511 1515 </t> 1512 1516
Note: See TracChangeset
for help on using the changeset viewer.