Changeset 2318
- Timestamp:
- 28/07/13 10:28:18 (9 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r2317 r2318 1410 1410 <h3 id="rfc.section.4.3.2"><a href="#rfc.section.4.3.2">4.3.2</a> <a id="HEAD" href="#HEAD">HEAD</a></h3> 1411 1411 <div id="rfc.iref.h.1"></div> 1412 <p id="rfc.section.4.3.2.p.1">The HEAD method is identical to GET except that the server <em class="bcp14">MUST NOT</em> send a message body in the response (i.e., the response terminates at the end of the header block). Aside from the payload 1413 header fields (<a href="#payload" title="Payload Semantics">Section 3.3</a>), the server <em class="bcp14">SHOULD</em> send the same header fields in response to a HEAD request as it would have sent if the request had been a GET. This method 1414 can be used for obtaining metadata about the selected representation without transferring the representation data. This method 1415 is often used for testing hypertext links for validity, accessibility, and recent modification. 1412 <p id="rfc.section.4.3.2.p.1">The HEAD method is identical to GET except that the server <em class="bcp14">MUST NOT</em> send a message body in the response (i.e., the response terminates at the end of the header block). The server <em class="bcp14">SHOULD</em> send the same header fields in response to a HEAD request as it would have sent if the request had been a GET, except that 1413 the payload header fields (<a href="#payload" title="Payload Semantics">Section 3.3</a>) <em class="bcp14">MAY</em> be omitted. This method can be used for obtaining metadata about the selected representation without transferring the representation 1414 data and is often used for testing hypertext links for validity, accessibility, and recent modification. 1416 1415 </p> 1417 1416 <p id="rfc.section.4.3.2.p.2">A payload within a HEAD request message has no defined semantics; sending a payload body on a HEAD request might cause some … … 4526 4525 <ul> 4527 4526 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/303">http://tools.ietf.org/wg/httpbis/trac/ticket/303</a>>: "400 response isn't generic" 4527 </li> 4528 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/451">http://tools.ietf.org/wg/httpbis/trac/ticket/451</a>>: "Content-Length in HEAD responses" 4528 4529 </li> 4529 4530 </ul> -
draft-ietf-httpbis/latest/p2-semantics.xml
r2317 r2318 1314 1314 The HEAD method is identical to GET except that the server &MUST-NOT; 1315 1315 send a message body in the response (i.e., the response terminates at the 1316 end of the header block). Aside from the payload header fields 1317 (<xref target="payload"/>), the server &SHOULD; send the same header fields 1316 end of the header block). The server &SHOULD; send the same header fields 1318 1317 in response to a HEAD request as it would have sent if the request had been 1319 a GET. This method can be used for obtaining metadata about the selected 1320 representation without transferring the representation data. This method is 1318 a GET, except that the payload header fields (<xref target="payload"/>) 1319 &MAY; be omitted. This method can be used for obtaining metadata about the 1320 selected representation without transferring the representation data and is 1321 1321 often used for testing hypertext links for validity, accessibility, and 1322 1322 recent modification. … … 6396 6396 "400 response isn't generic" 6397 6397 </t> 6398 <t> 6399 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/451"/>: 6400 "Content-Length in HEAD responses" 6401 </t> 6398 6402 </list> 6399 6403 </t>
Note: See TracChangeset
for help on using the changeset viewer.