Changeset 2071 for draft-ietf-httpbis/latest/p2-semantics.xml
- Timestamp:
- 31/12/12 06:09:31 (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.xml
r2070 r2071 480 480 </artwork></figure> 481 481 <t> 482 A sender &SHOULD; include a Content-Type header field in a message483 containing a payload body, defining the media type of the enclosed484 representation, unless the intended media typeis unknown to the sender.482 A sender that generates a message containing a payload body &SHOULD; 483 generate a Content-Type header field in that message unless the intended 484 media type of the enclosed representation is unknown to the sender. 485 485 If a Content-Type header field is not present, recipients &MAY; either 486 486 assume a media type of … … 1672 1672 <iref primary="true" item="TRACE method" x:for-anchor=""/> 1673 1673 <t> 1674 The TRACE method requests a remote, application-level loop-back 1675 of the request message. The final recipient of the request 1676 &SHOULD; reflect the message received back to the client as the message body 1677 of a <x:ref>200 (OK)</x:ref> response. The final recipient is either the 1678 origin server or the first proxy to receive a <x:ref>Max-Forwards</x:ref> 1679 value of zero (0) in the request (see <xref target="header.max-forwards"/>). 1680 A TRACE request &MUST-NOT; include a message body. 1674 The TRACE method requests a remote, application-level loop-back of the 1675 request message. The final recipient of the request &SHOULD; reflect the 1676 message received, excluding some fields described below, back to the client 1677 as the message body of a <x:ref>200 (OK)</x:ref> response with a 1678 <x:ref>Content-Type</x:ref> of "message/http" (&media-type-message-http;). 1679 The final recipient is either the origin server or the first server to 1680 receive a <x:ref>Max-Forwards</x:ref> value of zero (0) in the request 1681 (<xref target="header.max-forwards"/>). 1682 </t> 1683 <t> 1684 A client &MUST-NOT; send a message body in a TRACE request. 1685 </t> 1686 <t> 1687 A client &MUST-NOT; send header fields in a TRACE request containing 1688 sensitive data that might be disclosed by the response. For example, it 1689 would be foolish for a user agent to send stored user credentials 1690 <xref target="Part7"/> or cookies <xref target="RFC6265"/> in a TRACE 1691 request. The final recipient &SHOULD; exclude any request header fields 1692 from the response body that are likely to contain sensitive data. 1681 1693 </t> 1682 1694 <t> … … 1686 1698 is of particular interest, since it acts as a trace of the request chain. 1687 1699 Use of the <x:ref>Max-Forwards</x:ref> header field allows the client to 1688 limit the length of the request chain, which is useful for testing a chain of 1689 proxies forwarding messages in an infinite loop. 1690 </t> 1691 <t> 1692 If the request is valid, the response &SHOULD; have a 1693 <x:ref>Content-Type</x:ref> of "message/http" (see &media-type-message-http;) 1694 and contain a message body that encloses a copy of the entire request message. 1700 limit the length of the request chain, which is useful for testing a chain 1701 of proxies forwarding messages in an infinite loop. 1702 </t> 1703 <t> 1695 1704 Responses to the TRACE method are not cacheable. 1696 1705 </t> … … 5511 5520 </reference> 5512 5521 5522 <reference anchor="RFC6265"> 5523 <front> 5524 <title>HTTP State Management Mechanism</title> 5525 <author initials="A." surname="Barth" fullname="Adam Barth"> 5526 <organization abbrev="U.C. Berkeley"> 5527 University of California, Berkeley 5528 </organization> 5529 <address><email>abarth@eecs.berkeley.edu</email></address> 5530 </author> 5531 <date year="2011" month="April" /> 5532 </front> 5533 <seriesInfo name="RFC" value="6265"/> 5534 </reference> 5535 5513 5536 <reference anchor="RFC6266"> 5514 5537 <front>
Note: See TracChangeset
for help on using the changeset viewer.