Changeset 1868
- Timestamp:
- 06/09/12 06:52:52 (11 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 4 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r1867 r1868 1662 1662 that a client can be assured of buffering the entire response. 1663 1663 </p> 1664 <p id="rfc.section.4.3.p.7">When multiple transfer-codings are acceptable, the client <em class="bcp14">MAY</em> rank the codings by preference using a "q" parameter (similar to the qvalues used in content negotiation fields, <a href="p2-semantics.html#quality.values" title="Quality Values">Section 6.3.1</a> of <a href="#Part2" id="rfc.xref.Part2.11"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>). The rank value is a real number in the range 0 through 1, where 0.001 is the least preferred and 1 is the most preferred; 1664 <p id="rfc.section.4.3.p.7">When multiple transfer-codings are acceptable, the client <em class="bcp14">MAY</em> rank the codings by preference using a case-insensitive "q" parameter (similar to the qvalues used in content negotiation 1665 fields, <a href="p2-semantics.html#quality.values" title="Quality Values">Section 6.3.1</a> of <a href="#Part2" id="rfc.xref.Part2.11"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>). The rank value is a real number in the range 0 through 1, where 0.001 is the least preferred and 1 is the most preferred; 1665 1666 a value of 0 means "not acceptable". 1666 1667 </p> -
draft-ietf-httpbis/latest/p1-messaging.xml
r1867 r1868 2083 2083 <t> 2084 2084 When multiple transfer-codings are acceptable, the client &MAY; rank the 2085 codings by preference using a "q" parameter (similar to the qvalues2086 used in content negotiation fields, &qvalue;). The rank value is a real2087 number in the range 0 through 1, where 0.001 is the least preferred and2088 1 is the most preferred; a value of 0 means "not acceptable".2085 codings by preference using a case-insensitive "q" parameter (similar to 2086 the qvalues used in content negotiation fields, &qvalue;). The rank value 2087 is a real number in the range 0 through 1, where 0.001 is the least 2088 preferred and 1 is the most preferred; a value of 0 means "not acceptable". 2089 2089 </t> 2090 2090 <t> -
draft-ietf-httpbis/latest/p2-semantics.html
r1867 r1868 1766 1766 </div> 1767 1767 <h3 id="rfc.section.6.3.1"><a href="#rfc.section.6.3.1">6.3.1</a> <a id="quality.values" href="#quality.values">Quality Values</a></h3> 1768 <p id="rfc.section.6.3.1.p.1">Many of the request header fields for proactive content negotiation use a common parameter, named "q" , to assign a relative1769 "weight" to the preference for that associated kind of content. This weight is referred to as a "quality value" (or "qvalue")1770 because the same parameter name is often used within server configurations to assign a weight to the relative quality ofthe1771 various representations that can be selected for a resource.1768 <p id="rfc.section.6.3.1.p.1">Many of the request header fields for proactive content negotiation use a common parameter, named "q" (case-insensitive), 1769 to assign a relative "weight" to the preference for that associated kind of content. This weight is referred to as a "quality 1770 value" (or "qvalue") because the same parameter name is often used within server configurations to assign a weight to the 1771 relative quality of the various representations that can be selected for a resource. 1772 1772 </p> 1773 1773 <p id="rfc.section.6.3.1.p.2">The weight is normalized to a real number in the range 0 through 1, where 0.001 is the least preferred and 1 is the most preferred; -
draft-ietf-httpbis/latest/p2-semantics.xml
r1867 r1868 1822 1822 <t> 1823 1823 Many of the request header fields for proactive content negotiation 1824 use a common parameter, named "q" , to assign a relative "weight" to the1825 preference for that associated kind of content.1824 use a common parameter, named "q" (case-insensitive), to assign a relative 1825 "weight" to the preference for that associated kind of content. 1826 1826 This weight is referred to as a "quality value" (or "qvalue") because 1827 1827 the same parameter name is often used within server configurations to
Note: See TracChangeset
for help on using the changeset viewer.