Changeset 908
- Timestamp:
- 24/07/10 08:30:41 (12 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 4 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"/>), -
draft-ietf-httpbis/latest/p4-conditional.xml
r879 r908 357 357 </artwork></figure> 358 358 <t> 359 In this case, the response m ay or maynot use the gzip content coding.359 In this case, the response might or might not use the gzip content coding. 360 360 If it does not, the response might look like: 361 361 </t> … … 1074 1074 The exact meaning of this header field depends on the implementation 1075 1075 of the origin server and the nature of the original resource. For 1076 files, it m aybe just the file system last-modified time. For1077 representations with dynamically included parts, it m aybe the most recent1076 files, it might be just the file system last-modified time. For 1077 representations with dynamically included parts, it might be the most recent 1078 1078 of the set of last-modify times for its component parts. For database 1079 gateways, it m aybe the last-update time stamp of the record. For1080 virtual objects, it m aybe the last time the internal state changed.1079 gateways, it might be the last-update time stamp of the record. For 1080 virtual objects, it might be the last time the internal state changed. 1081 1081 </t> 1082 1082 <t> -
draft-ietf-httpbis/latest/p5-range.xml
r874 r908 1287 1287 Notes: 1288 1288 <list style="numbers"> 1289 <t>Additional CRLFs mayprecede the first boundary string in the body.</t>1289 <t>Additional CRLFs &MAY; precede the first boundary string in the body.</t> 1290 1290 1291 1291 <t>Although <xref target="RFC2046"/> permits the boundary string to be -
draft-ietf-httpbis/latest/p6-cache.xml
r897 r908 237 237 controls its message storage, retrieval, and deletion. A cache stores cacheable responses 238 238 in order to reduce the response time and network bandwidth consumption on future, 239 equivalent requests. Any client or server may includea cache, though a cache cannot be239 equivalent requests. Any client or server &MAY; employ a cache, though a cache cannot be 240 240 used by a server that is acting as a tunnel. 241 241 </t> … … 262 262 <list> 263 263 <t>A response is cacheable if a cache is allowed to store a copy of the response message 264 for use in answering subsequent requests. Even when a response is cacheable, there m ay264 for use in answering subsequent requests. Even when a response is cacheable, there might 265 265 be additional constraints on whether a cache can use the cached copy to satisfy a 266 266 particular request.</t> … … 537 537 assign an explicit expiration time in the past. This means that the response is always 538 538 stale, so that caches should validate it before using it for subsequent requests. 539 <cref anchor="TODO-response-stale">This wording m ay cause confusion, because the response maystill be served stale.</cref>540 </t> 541 <t> 542 Since origin servers do not always provide explicit expiration times, HTTP caches may543 a lso assign heuristic expiration times when theyare not specified, employing algorithms that539 <cref anchor="TODO-response-stale">This wording might cause confusion, because the response might still be served stale.</cref> 540 </t> 541 <t> 542 Since origin servers do not always provide explicit expiration times, HTTP caches &MAY; 543 assign heuristic expiration times when explicit times are not specified, employing algorithms that 544 544 use other header values (such as the Last-Modified time) to estimate a plausible 545 545 expiration time. The HTTP/1.1 specification does not provide specific algorithms, but does … … 559 559 </t> 560 560 <t> 561 Additionally, clients m ayneed to influence freshness calculation. They can do this using561 Additionally, clients might need to influence freshness calculation. They can do this using 562 562 several request cache directives, with the effect of either increasing or loosening 563 563 constraints on freshness. See <xref target="cache-request-directive" />. … … 874 874 </t> 875 875 <t> 876 If (after any normali sation that maytake place) a header field is absent876 If (after any normalization that might take place) a header field is absent 877 877 from a request, it can only match another request if it is also absent there. 878 878 </t> … … 899 899 <t> 900 900 If the new response contains an ETag, it identifies the stored 901 response to use. <cref anchor="TODO-mention-CL">m ayneed language about Content-Location901 response to use. <cref anchor="TODO-mention-CL">might need language about Content-Location 902 902 here</cref><cref anchor="TODO-inm-mult-etags">cover case where INM with multiple etags was sent</cref> 903 903 </t> … … 973 973 <t> 974 974 The presence of an Age header field in a response implies that a response is not 975 first-hand. However, the converse is not true, since HTTP/1.0 caches m aynot implement the975 first-hand. However, the converse is not true, since HTTP/1.0 caches might not implement the 976 976 Age header field. 977 977 </t> … … 1057 1057 <t>This directive is NOT a reliable or sufficient mechanism for ensuring privacy. In 1058 1058 particular, malicious or compromised caches might not recognize or obey this 1059 directive, and communications networks m aybe vulnerable to eavesdropping.</t>1059 directive, and communications networks might be vulnerable to eavesdropping.</t> 1060 1060 </list> 1061 1061 </t> … … 1159 1159 cache, whereas the remainder of the response message &MAY; be.</t> 1160 1160 <t> 1161 <x:h>Note:</x:h> This usage of the word private only controls where the response may1162 be stored , andcannot ensure the privacy of the message content.1161 <x:h>Note:</x:h> This usage of the word private only controls where the response can 1162 be stored; it cannot ensure the privacy of the message content. 1163 1163 Also, private response directives with field-names are often handled by 1164 1164 implementations as if an unqualified private directive was received; i.e., … … 1203 1203 <t>This directive is NOT a reliable or sufficient mechanism for ensuring privacy. In 1204 1204 particular, malicious or compromised caches might not recognize or obey this 1205 directive, and communications networks m aybe vulnerable to eavesdropping.</t>1205 directive, and communications networks might be vulnerable to eavesdropping.</t> 1206 1206 </list> 1207 1207 </t> … … 1451 1451 request-headers (e.g., the network address of the client), play a role in the selection of 1452 1452 the response representation; therefore, a cache cannot determine whether this response is 1453 appropriate. The "*" value &MUST-NOT; be generated by a proxy server; 1454 it may only be generated by an origin server. 1453 appropriate. The "*" value &MUST-NOT; be generated by a proxy server. 1455 1454 </t> 1456 1455 <t>
Note: See TracChangeset
for help on using the changeset viewer.