Changeset 1036


Ignore:
Timestamp:
Oct 19, 2010, 2:32:23 AM (9 years ago)
Author:
julian.reschke@…
Message:

Source reformat, update Changes section (see #232 and [1032])

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

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.html

    r1031 r1036  
    404404      <meta name="dct.creator" content="Reschke, J. F.">
    405405      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest">
    406       <meta name="dct.issued" scheme="ISO8601" content="2010-10-14">
     406      <meta name="dct.issued" scheme="ISO8601" content="2010-10-19">
    407407      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    408408      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 1 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 1 provides an overview of HTTP and its associated terminology, defines the &#34;http&#34; and &#34;https&#34; Uniform Resource Identifier (URI) schemes, defines the generic message syntax and parsing requirements for HTTP message frames, and describes general security concerns for implementations.">
     
    435435            </tr>
    436436            <tr>
    437                <td class="left">Expires: April 17, 2011</td>
     437               <td class="left">Expires: April 22, 2011</td>
    438438               <td class="right">HP</td>
    439439            </tr>
     
    488488            <tr>
    489489               <td class="left"></td>
    490                <td class="right">October 14, 2010</td>
     490               <td class="right">October 19, 2010</td>
    491491            </tr>
    492492         </tbody>
     
    516516         in progress”.
    517517      </p>
    518       <p>This Internet-Draft will expire on April 17, 2011.</p>
     518      <p>This Internet-Draft will expire on April 22, 2011.</p>
    519519      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    520520      <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
  • draft-ietf-httpbis/latest/p2-semantics.html

    r1035 r1036  
    26192619      </ul>
    26202620      <h2 id="rfc.section.C.13"><a href="#rfc.section.C.13">C.13</a>&nbsp;<a id="changes.since.11" href="#changes.since.11">Since draft-ietf-httpbis-p2-semantics-11</a></h2>
    2621       <p id="rfc.section.C.13.p.1">None yet.</p>
     2621      <p id="rfc.section.C.13.p.1">Closed issues: </p>
     2622      <ul>
     2623         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/232">http://tools.ietf.org/wg/httpbis/trac/ticket/232</a>&gt;: "User-Agent guidelines" (relating to the 'User-Agent' header field)
     2624         </li>
     2625      </ul>
    26222626      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
    26232627      <p class="noprint"><a href="#rfc.index.1">1</a> <a href="#rfc.index.2">2</a> <a href="#rfc.index.3">3</a> <a href="#rfc.index.4">4</a> <a href="#rfc.index.5">5</a> <a href="#rfc.index.A">A</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.D">D</a> <a href="#rfc.index.E">E</a> <a href="#rfc.index.F">F</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.L">L</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.O">O</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> <a href="#rfc.index.T">T</a> <a href="#rfc.index.U">U</a>
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r1035 r1036  
    23442344  <x:anchor-alias value="User-Agent"/>
    23452345  <x:anchor-alias value="User-Agent-v"/>
    2346 
    2347   <t>The "User-Agent" request-header field contains information about the user
    2348   agent originating the request. User agents &SHOULD; include this field with
    2349   requests.</t>
    2350 
    2351   <t>Typically, it is used for statistical purposes, the tracing of protocol
    2352   violations, and tailoring responses to avoid particular user agent
    2353   limitations.</t>
    2354 
    2355   <t>The field can contain multiple product tokens (&product-tokens;)
    2356   and comments (&header-fields;) identifying the agent and its
    2357   significant subproducts. By convention, the product tokens are listed in
    2358   order of their significance for identifying the application.</t>
    2359 
    2360   <t>Because this field is usually sent on every request a user agent makes,
    2361   implementations are encouraged not to include needlessly fine-grained
    2362   detail, and to limit (or even prohibit) the addition of subproducts by third
    2363   parties. Overly long and detailed User-Agent field values make requests
    2364   larger and can also be used to identify ("fingerprint") the user against
    2365   their wishes.</t>
    2366 
    2367   <t>Likewise, implementations are encouraged not to use the product tokens of
    2368   other implementations in order to declare compatibility with them, as this
    2369   circumvents the purpose of the field. Finally, they are encouraged not to
    2370   use comments to identify products; doing so makes the field value more
    2371   difficult to parse.</t>
    2372 
     2346<t>
     2347   The "User-Agent" request-header field contains information about the user
     2348   agent originating the request. User agents &SHOULD; include this field with
     2349   requests.
     2350</t>
     2351<t>
     2352   Typically, it is used for statistical purposes, the tracing of protocol
     2353   violations, and tailoring responses to avoid particular user agent
     2354   limitations.
     2355</t>
     2356<t>
     2357   The field can contain multiple product tokens (&product-tokens;)
     2358   and comments (&header-fields;) identifying the agent and its
     2359   significant subproducts. By convention, the product tokens are listed in
     2360   order of their significance for identifying the application.
     2361</t>
     2362<t>
     2363   Because this field is usually sent on every request a user agent makes,
     2364   implementations are encouraged not to include needlessly fine-grained
     2365   detail, and to limit (or even prohibit) the addition of subproducts by third
     2366   parties. Overly long and detailed User-Agent field values make requests
     2367   larger and can also be used to identify ("fingerprint") the user against
     2368   their wishes.
     2369</t>
     2370<t>
     2371   Likewise, implementations are encouraged not to use the product tokens of
     2372   other implementations in order to declare compatibility with them, as this
     2373   circumvents the purpose of the field. Finally, they are encouraged not to
     2374   use comments to identify products; doing so makes the field value more
     2375   difficult to parse.
     2376</t>
    23732377<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="User-Agent"/><iref primary="true" item="Grammar" subitem="User-Agent-v"/>
    23742378  <x:ref>User-Agent</x:ref>     = "User-Agent" ":" <x:ref>OWS</x:ref> <x:ref>User-Agent-v</x:ref>
     
    27772781   Referer information.
    27782782</t>
    2779 
    2780   <t>The User-Agent (<xref target="header.user-agent"/>) or Server (<xref
    2781   target="header.server"/>) header fields can sometimes be used to determine
    2782   that a specific client or server have a particular security hole which might
    2783   be exploited. Unfortunately, this same information is often used for other
    2784   valuable purposes for which HTTP currently has no better mechanism.</t>
    2785 
    2786   <t>Furthermore, the User-Agent header field may contain enough entropy to be
    2787   used, possibly in conjunction with other material, to uniquely identify the
    2788   user.</t>
    2789 
     2783<t>
     2784   The User-Agent (<xref target="header.user-agent"/>) or Server (<xref
     2785   target="header.server"/>) header fields can sometimes be used to determine
     2786   that a specific client or server have a particular security hole which might
     2787   be exploited. Unfortunately, this same information is often used for other
     2788   valuable purposes for which HTTP currently has no better mechanism.
     2789</t>
     2790<t>
     2791   Furthermore, the User-Agent header field may contain enough entropy to be
     2792   used, possibly in conjunction with other material, to uniquely identify the
     2793   user.
     2794</t>
    27902795<t>
    27912796   Some methods, like TRACE (<xref target="TRACE"/>), expose information
     
    38733878<section title="Since draft-ietf-httpbis-p2-semantics-11" anchor="changes.since.11">
    38743879<t>
    3875   None yet.
     3880  Closed issues:
     3881  <list style="symbols">
     3882    <t>
     3883      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/232"/>:
     3884      "User-Agent guidelines" (relating to the 'User-Agent' header field)
     3885    </t>
     3886  </list>
    38763887</t>
    38773888</section>
  • draft-ietf-httpbis/latest/p7-auth.html

    r1026 r1036  
    397397      <meta name="dct.creator" content="Reschke, J. F.">
    398398      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p7-auth-latest">
    399       <meta name="dct.issued" scheme="ISO8601" content="2010-10-07">
     399      <meta name="dct.issued" scheme="ISO8601" content="2010-10-19">
    400400      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    401401      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 7 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 7 defines HTTP Authentication.">
     
    428428            </tr>
    429429            <tr>
    430                <td class="left">Expires: April 10, 2011</td>
     430               <td class="left">Expires: April 22, 2011</td>
    431431               <td class="right">HP</td>
    432432            </tr>
     
    481481            <tr>
    482482               <td class="left"></td>
    483                <td class="right">October 7, 2010</td>
     483               <td class="right">October 19, 2010</td>
    484484            </tr>
    485485         </tbody>
     
    507507         in progress”.
    508508      </p>
    509       <p>This Internet-Draft will expire on April 10, 2011.</p>
     509      <p>This Internet-Draft will expire on April 22, 2011.</p>
    510510      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    511511      <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
Note: See TracChangeset for help on using the changeset viewer.