Ignore:
Timestamp:
Feb 3, 2008, 11:07:03 AM (12 years ago)
Author:
julian.reschke@…
Message:

Move Section "Product Tokens" from P2 into P1 (back below "Protocol Parameters") ("token" is used in the definition of the Upgrade header); addresses #36.

File:
1 edited

Legend:

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

    r184 r190  
    5656  <!ENTITY header-www-authenticate    "<xref target='Part7' x:rel='#header.www-authenticate' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    5757  <!ENTITY message-body               "<xref target='Part1' x:rel='#message.body' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     58  <!ENTITY product-tokens             "<xref target='Part1' x:rel='#product.tokens' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    5859]>
    5960<?rfc toc="yes" ?>
     
    283284</section>
    284285
    285 <section title="Product Tokens" anchor="product.tokens">
    286 <t>
    287    Product tokens are used to allow communicating applications to
    288    identify themselves by software name and version. Most fields using
    289    product tokens also allow sub-products which form a significant part
    290    of the application to be listed, separated by white space. By
    291    convention, the products are listed in order of their significance
    292    for identifying the application.
    293 </t>
    294 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="product"/><iref primary="true" item="Grammar" subitem="product-version"/>
    295   product         = token ["/" product-version]
    296   product-version = token
    297 </artwork></figure>
    298 <t>
    299    Examples:
    300 </t>
    301 <figure><artwork type="example">
    302     User-Agent: CERN-LineMode/2.15 libwww/2.17b3
    303     Server: Apache/0.8.4
    304 </artwork></figure>
    305 <t>
    306    Product tokens &SHOULD; be short and to the point. They &MUST-NOT; be
    307    used for advertising or other non-essential information. Although any
    308    token character &MAY; appear in a product-version, this token &SHOULD;
    309    only be used for a version identifier (i.e., successive versions of
    310    the same product &SHOULD; only differ in the product-version portion of
    311    the product value).
    312 </t>
    313 </section>
    314 
    315286<section title="Method" anchor="method">
    316287<t>
     
    19211892   The Server response-header field contains information about the
    19221893   software used by the origin server to handle the request. The field
    1923    can contain multiple product tokens (<xref target="product.tokens"/>) and comments
     1894   can contain multiple product tokens (&product-tokens;) and comments
    19241895   identifying the server and any significant subproducts. The product
    19251896   tokens are listed in order of their significance for identifying the
     
    19581929   agents for the sake of tailoring responses to avoid particular user
    19591930   agent limitations. User agents &SHOULD; include this field with
    1960    requests. The field can contain multiple product tokens (<xref target="product.tokens"/>)
     1931   requests. The field can contain multiple product tokens (&product-tokens;)
    19611932   and comments identifying the agent and any subproducts which form a
    19621933   significant part of the user agent. By convention, the product tokens
     
    26372608  </list>
    26382609</t>
     2610<t>
     2611  Ongoing work on ABNF conversion (<eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/36"/>):
     2612  <list style="symbols">
     2613    <t>
     2614      Move "Product Tokens" section (back) into Part 1, as "token" is used
     2615      in the definition of the Upgrade header.
     2616    </t>
     2617  </list>
     2618</t>
    26392619</section>
    26402620
Note: See TracChangeset for help on using the changeset viewer.