Changeset 2562
- Timestamp:
- 19/01/14 03:22:35 (8 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r2561 r2562 2731 2731 </p> 2732 2732 <p id="rfc.section.6.4.1.p.3">For request methods other than HEAD, the server <em class="bcp14">SHOULD</em> generate a payload in the 300 response containing a list of representation metadata and URI reference(s) from which the user 2733 or user agent can choose the one most preferred. The user agent <em class="bcp14">MAY</em> make a selection from that list automatically, depending upon the list format, but this specification does not define a standard 2734 for such automatic selection. 2733 or user agent can choose the one most preferred. The user agent <em class="bcp14">MAY</em> make a selection from that list automatically if it understands the provided media type. A specific format for automatic selection 2734 is not defined by this specification because HTTP tries to remain orthogonal to the definition of its payloads. In practice, 2735 the representation is provided in some easily parsed format believed to be acceptable to the user agent, as determined by 2736 shared design or content negotiation, or in some commonly accepted hypertext format. 2735 2737 </p> 2736 2738 <p id="rfc.section.6.4.1.p.4">A 300 response is cacheable by default; i.e., unless otherwise indicated by the method definition or explicit cache controls -
draft-ietf-httpbis/latest/p2-semantics.xml
r2561 r2562 3097 3097 reference(s) from which the user or user agent can choose the one most 3098 3098 preferred. The user agent &MAY; make a selection from that list 3099 automatically, depending upon the list format, but this specification does 3100 not define a standard for such automatic selection. 3099 automatically if it understands the provided media type. A specific format 3100 for automatic selection is not defined by this specification because HTTP 3101 tries to remain orthogonal to the definition of its payloads. 3102 In practice, the representation is provided in some easily parsed format 3103 believed to be acceptable to the user agent, as determined by shared design 3104 or content negotiation, or in some commonly accepted hypertext format. 3101 3105 </t> 3102 3106 <t>
Note: See TracChangeset
for help on using the changeset viewer.