Changeset 908 for draft-ietf-httpbis/latest/p3-payload.xml
- Timestamp:
- 24/07/10 08:30:41 (12 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p3-payload.xml
r882 r908 230 230 associated metadata header fields that define how the payload is intended 231 231 to be interpreted by a recipient, the request header fields that 232 m ayinfluence content selection, and the various selection algorithms232 might influence content selection, and the various selection algorithms 233 233 that are collectively referred to as HTTP content negotiation. 234 234 </t> … … 394 394 method used with one or more tables to convert a sequence of octets 395 395 into a sequence of characters. Note that unconditional conversion in 396 the other direction is not required, in that not all characters m ay397 be available in a given character set and a character set m ayprovide396 the other direction is not required, in that not all characters might 397 be available in a given character set and a character set might provide 398 398 more than one sequence of octets to represent a particular character. 399 399 This definition is intended to allow various kinds of character … … 434 434 value of a parameter in a Content-Type header (within a request or 435 435 response), in which case the parameter value of the charset parameter 436 maybe quoted.436 can be quoted. 437 437 </t> 438 438 <t> … … 583 583 </t> 584 584 <t> 585 A parameter value that matches the <x:ref>token</x:ref> production maybe585 A parameter value that matches the <x:ref>token</x:ref> production can be 586 586 transmitted as either a token or within a quoted-string. The quoted and 587 587 unquoted values are equivalent. … … 790 790 </t> 791 791 <t> 792 Clients that do so risk drawing incorrect conclusions, which m ayexpose792 Clients that do so risk drawing incorrect conclusions, which might expose 793 793 additional security risks (e.g., "privilege escalation"). Implementers are 794 794 encouraged to provide a means of disabling such "content sniffing" when it … … 796 796 </t> 797 797 <t> 798 Content-Encoding may beused to indicate any additional content798 Content-Encoding is used to indicate any additional content 799 799 codings applied to the data, usually for the purpose of data 800 800 compression, that are a property of the representation. There is … … 840 840 capabilities to be expressed by a client are large (such as when many 841 841 different formats are supported by a user-agent), server-driven 842 negotiation becomes unwieldy, and m aynot be appropriate. Conversely,842 negotiation becomes unwieldy, and might not be appropriate. Conversely, 843 843 when the number of representations to choose from is very large, 844 agent-driven negotiation m aynot be appropriate.844 agent-driven negotiation might not be appropriate. 845 845 </t> 846 846 <t> … … 892 892 </t> 893 893 <t> 894 It m aylimit a public cache's ability to use the same response894 It might limit a public cache's ability to use the same response 895 895 for multiple user's requests. 896 896 </t> … … 929 929 header fields or body of the initial response, with each 930 930 representation identified by its own URI. Selection from among the 931 representations maybe performed automatically (if the user agent is931 representations can be performed automatically (if the user agent is 932 932 capable of doing so) or manually by the user selecting from a 933 933 generated (possibly hypertext) menu. … … 1455 1455 contains a report on the action's status and the same report is 1456 1456 available (for future access with GET) at the given URI. For 1457 example, a purchase transaction made via the POST method m ay1457 example, a purchase transaction made via the POST method might 1458 1458 include a receipt document as the payload of the 200 response; 1459 1459 the Content-Location value provides an identifier for retrieving … … 2064 2064 <seriesInfo name="RFC" value="1950"/> 2065 2065 <annotation> 2066 RFC 1950 is an Informational RFC, thus it m aybe less stable than2066 RFC 1950 is an Informational RFC, thus it might be less stable than 2067 2067 this specification. On the other hand, this downward reference was 2068 2068 present since the publication of RFC 2068 in 1997 (<xref target="RFC2068"/>), … … 2083 2083 <seriesInfo name="RFC" value="1951"/> 2084 2084 <annotation> 2085 RFC 1951 is an Informational RFC, thus it m aybe less stable than2085 RFC 1951 is an Informational RFC, thus it might be less stable than 2086 2086 this specification. On the other hand, this downward reference was 2087 2087 present since the publication of RFC 2068 in 1997 (<xref target="RFC2068"/>), … … 2114 2114 <seriesInfo name="RFC" value="1952"/> 2115 2115 <annotation> 2116 RFC 1952 is an Informational RFC, thus it m aybe less stable than2116 RFC 1952 is an Informational RFC, thus it might be less stable than 2117 2117 this specification. On the other hand, this downward reference was 2118 2118 present since the publication of RFC 2068 in 1997 (<xref target="RFC2068"/>),
Note: See TracChangeset
for help on using the changeset viewer.