Changeset 2104


Ignore:
Timestamp:
Jan 10, 2013, 1:11:48 AM (7 years ago)
Author:
fielding@…
Message:

(editorial) add intro for proactive negotiation fields and clarify that they might apply to any response content, not just representations of the target resource

Location:
draft-ietf-httpbis/latest
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.html

    r2103 r2104  
    17761776      </div>
    17771777      <h2 id="rfc.section.5.3"><a href="#rfc.section.5.3">5.3</a>&nbsp;<a id="request.conneg" href="#request.conneg">Content Negotiation</a></h2>
     1778      <p id="rfc.section.5.3.p.1">The following request header fields are sent by a user agent to engage in <a href="#proactive.negotiation" class="smpl">proactive negotiation</a> of the response content, as defined in <a href="#proactive.negotiation" title="Proactive Negotiation">Section&nbsp;3.4.1</a>. The preferences sent in these fields apply to any content in the response, including representations of the target resource,
     1779         representations of error or processing status, and potentially even the miscellaneous text strings that might appear within
     1780         the protocol.
     1781      </p>
    17781782      <div id="rfc.table.u.5">
    17791783         <table class="tt full left" cellpadding="3" cellspacing="0">
     
    18051809      </div>
    18061810      <h3 id="rfc.section.5.3.1"><a href="#rfc.section.5.3.1">5.3.1</a>&nbsp;<a id="quality.values" href="#quality.values">Quality Values</a></h3>
    1807       <p id="rfc.section.5.3.1.p.1">Many of the request header fields for proactive content negotiation use a common parameter, named "q" (case-insensitive),
    1808          to assign a relative "weight" to the preference for that associated kind of content. This weight is referred to as a "quality
    1809          value" (or "qvalue") because the same parameter name is often used within server configurations to assign a weight to the
    1810          relative quality of the various representations that can be selected for a resource.
     1811      <p id="rfc.section.5.3.1.p.1">Many of the request header fields for <a href="#proactive.negotiation" class="smpl">proactive negotiation</a> use a common parameter, named "q" (case-insensitive), to assign a relative "weight" to the preference for that associated
     1812         kind of content. This weight is referred to as a "quality value" (or "qvalue") because the same parameter name is often used
     1813         within server configurations to assign a weight to the relative quality of the various representations that can be selected
     1814         for a resource.
    18111815      </p>
    18121816      <p id="rfc.section.5.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;
     
    19191923      <div id="rfc.iref.a.2"></div>
    19201924      <h3 id="rfc.section.5.3.3"><a href="#rfc.section.5.3.3">5.3.3</a>&nbsp;<a id="header.accept-charset" href="#header.accept-charset">Accept-Charset</a></h3>
    1921       <p id="rfc.section.5.3.3.p.1">The "Accept-Charset" header field can be sent by a user agent to indicate what charsets are acceptable in a selected representation.
    1922          This field allows user agents capable of understanding more comprehensive or special-purpose charsets to signal that capability
    1923          to an origin server that is capable of representing documents in those charsets.
     1925      <p id="rfc.section.5.3.3.p.1">The "Accept-Charset" header field can be sent by a user agent to indicate what charsets are acceptable in textual response
     1926         content. This field allows user agents capable of understanding more comprehensive or special-purpose charsets to signal that
     1927         capability to an origin server that is capable of representing information in those charsets.
    19241928      </p>
    19251929      <div id="rfc.figure.u.28"></div><pre class="inline"><span id="rfc.iref.g.29"></span>  <a href="#header.accept-charset" class="smpl">Accept-Charset</a> = 1#( ( <a href="#charset" class="smpl">charset</a> / "*" ) [ <a href="#quality.values" class="smpl">weight</a> ] )
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r2103 r2104  
    19721972
    19731973<section title="Content Negotiation" anchor="request.conneg">
     1974<t>
     1975   The following request header fields are sent by a user agent to engage in
     1976   <x:ref>proactive negotiation</x:ref> of the response content, as defined in
     1977   <xref target="proactive.negotiation"/>. The preferences sent in these
     1978   fields apply to any content in the response, including representations of
     1979   the target resource, representations of error or processing status, and
     1980   potentially even the miscellaneous text strings that might appear within
     1981   the protocol.
     1982</t>
    19741983<texttable align="left">
    19751984  <ttcol>Header Field Name</ttcol>
     
    19861995  <x:anchor-alias value="qvalue"/>
    19871996<t>
    1988    Many of the request header fields for proactive content negotiation
     1997   Many of the request header fields for <x:ref>proactive negotiation</x:ref>
    19891998   use a common parameter, named "q" (case-insensitive), to assign a relative
    19901999   "weight" to the preference for that associated kind of content.
     
    21432152<t>
    21442153   The "Accept-Charset" header field can be sent by a user agent to
    2145    indicate what charsets are acceptable in a selected representation.
     2154   indicate what charsets are acceptable in textual response content.
    21462155   This field allows user agents capable of understanding more comprehensive
    21472156   or special-purpose charsets to signal that capability to an origin server
    2148    that is capable of representing documents in those charsets.
     2157   that is capable of representing information in those charsets.
    21492158</t>
    21502159<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Accept-Charset"/>
Note: See TracChangeset for help on using the changeset viewer.