Changeset 1515 for draft-ietf-httpbis/latest/p2-semantics.xml
- Timestamp:
- 26/01/12 16:43:02 (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.xml
r1514 r1515 1406 1406 in the response. 1407 1407 </t> 1408 <t> 1409 For most status codes the response can carry a payload, in which case a 1410 Content-Type header field indicates the payload's media type 1411 (&header-content-type;). 1412 </t> 1408 1413 1409 1414 <section title="Informational 1xx" anchor="status.1xx"> … … 1511 1516 &SHOULD; include a payload containing a list of resource 1512 1517 characteristics and location(s) from which the user or user agent can 1513 choose the one most appropriate. The payload format is specified by 1514 the media type given in the Content-Type header field. 1518 choose the one most appropriate. 1515 1519 </t> 1516 1520 <t> … … 1731 1735 Unless it was a HEAD request, the response &SHOULD; include a representation 1732 1736 containing a list of representation metadata and location(s) from 1733 which the user or user agent can choose the one most appropriate. The 1734 data format is specified by the media type given in the Content-Type 1735 header field. Depending upon the format and the capabilities of 1737 which the user or user agent can choose the one most appropriate. Depending 1738 upon the format and the capabilities of 1736 1739 the user agent, selection of the most appropriate choice &MAY; be 1737 1740 performed automatically. However, this specification does not define … … 2027 2030 containing a list of available representation characteristics and location(s) 2028 2031 from which the user or user agent can choose the one most 2029 appropriate. The data format is specified by the media type given 2030 in the Content-Type header field. Depending upon the format and the 2032 appropriate. Depending upon the format and the 2031 2033 capabilities of the user agent, selection of the most appropriate 2032 2034 choice &MAY; be performed automatically. However, this specification … … 2088 2090 to indicate that it can't complete the request. In this case, the 2089 2091 response representation would likely contain a list of the differences 2090 between the two versions in a format defined by the response 2091 Content-Type. 2092 between the two versions. 2092 2093 </t> 2093 2094 </section>
Note: See TracChangeset
for help on using the changeset viewer.