Changeset 1036 for draft-ietf-httpbis

Timestamp:

19/10/10 09:32:23 (11 years ago)

Author:

julian.reschke@…

Message:

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

Location:

draft-ietf-httpbis/latest

Files:

• p1-messaging.html (modified) (4 diffs)
• p2-semantics.html (modified) (1 diff)
• p2-semantics.xml (modified) (3 diffs)
• p7-auth.html (modified) (4 diffs)

draft-ietf-httpbis/latest/p1-messaging.html

@@ -404 +404 @@
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2010-10-14">
+      <meta name="dct.issued" scheme="ISO8601" content="2010-10-19">
       <meta name="dct.replaces" content="urn:ietf:rfc:2616">
       <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.">
@@ -435 +435 @@
             </tr>
             <tr>
-               <td class="left">Expires: April 17, 2011</td>
+               <td class="left">Expires: April 22, 2011</td>
                <td class="right">HP</td>
             </tr>
@@ -488 +488 @@
             <tr>
                <td class="left"></td>
-               <td class="right">October 14, 2010</td>
+               <td class="right">October 19, 2010</td>
             </tr>
          </tbody>
@@ -516 +516 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on April 17, 2011.</p>
+      <p>This Internet-Draft will expire on April 22, 2011.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>

draft-ietf-httpbis/latest/p2-semantics.html

@@ -2619 +2619 @@
       </ul>
       <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>
-      <p id="rfc.section.C.13.p.1">None yet.</p>
+      <p id="rfc.section.C.13.p.1">Closed issues: </p>
+      <ul>
+         <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)
+         </li>
+      </ul>
       <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
       <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

@@ -2344 +2344 @@
   <x:anchor-alias value="User-Agent"/>
   <x:anchor-alias value="User-Agent-v"/>
-
-  <t>The "User-Agent" request-header field contains information about the user
-  agent originating the request. User agents &SHOULD; include this field with
-  requests.</t>
-
-  <t>Typically, it is used for statistical purposes, the tracing of protocol
-  violations, and tailoring responses to avoid particular user agent
-  limitations.</t>
-
-  <t>The field can contain multiple product tokens (&product-tokens;)
-  and comments (&header-fields;) identifying the agent and its
-  significant subproducts. By convention, the product tokens are listed in
-  order of their significance for identifying the application.</t>
-
-  <t>Because this field is usually sent on every request a user agent makes,
-  implementations are encouraged not to include needlessly fine-grained
-  detail, and to limit (or even prohibit) the addition of subproducts by third
-  parties. Overly long and detailed User-Agent field values make requests
-  larger and can also be used to identify ("fingerprint") the user against
-  their wishes.</t>
-
-  <t>Likewise, implementations are encouraged not to use the product tokens of
-  other implementations in order to declare compatibility with them, as this
-  circumvents the purpose of the field. Finally, they are encouraged not to
-  use comments to identify products; doing so makes the field value more
-  difficult to parse.</t>
-
+<t>
+   The "User-Agent" request-header field contains information about the user
+   agent originating the request. User agents &SHOULD; include this field with
+   requests.
+</t>
+<t>
+   Typically, it is used for statistical purposes, the tracing of protocol
+   violations, and tailoring responses to avoid particular user agent
+   limitations.
+</t>
+<t>
+   The field can contain multiple product tokens (&product-tokens;)
+   and comments (&header-fields;) identifying the agent and its
+   significant subproducts. By convention, the product tokens are listed in
+   order of their significance for identifying the application.
+</t>
+<t>
+   Because this field is usually sent on every request a user agent makes,
+   implementations are encouraged not to include needlessly fine-grained
+   detail, and to limit (or even prohibit) the addition of subproducts by third
+   parties. Overly long and detailed User-Agent field values make requests
+   larger and can also be used to identify ("fingerprint") the user against
+   their wishes.
+</t>
+<t>
+   Likewise, implementations are encouraged not to use the product tokens of
+   other implementations in order to declare compatibility with them, as this
+   circumvents the purpose of the field. Finally, they are encouraged not to
+   use comments to identify products; doing so makes the field value more
+   difficult to parse.
+</t>
 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="User-Agent"/><iref primary="true" item="Grammar" subitem="User-Agent-v"/>
   <x:ref>User-Agent</x:ref>     = "User-Agent" ":" <x:ref>OWS</x:ref> <x:ref>User-Agent-v</x:ref>
@@ -2777 +2781 @@
    Referer information.
 </t>
-
-  <t>The User-Agent (<xref target="header.user-agent"/>) or Server (<xref
-  target="header.server"/>) header fields can sometimes be used to determine
-  that a specific client or server have a particular security hole which might
-  be exploited. Unfortunately, this same information is often used for other
-  valuable purposes for which HTTP currently has no better mechanism.</t>
-
-  <t>Furthermore, the User-Agent header field may contain enough entropy to be
-  used, possibly in conjunction with other material, to uniquely identify the
-  user.</t>
-
+<t>
+   The User-Agent (<xref target="header.user-agent"/>) or Server (<xref
+   target="header.server"/>) header fields can sometimes be used to determine
+   that a specific client or server have a particular security hole which might
+   be exploited. Unfortunately, this same information is often used for other
+   valuable purposes for which HTTP currently has no better mechanism.
+</t>
+<t>
+   Furthermore, the User-Agent header field may contain enough entropy to be
+   used, possibly in conjunction with other material, to uniquely identify the
+   user.
+</t>
 <t>
    Some methods, like TRACE (<xref target="TRACE"/>), expose information
@@ -3873 +3878 @@
 <section title="Since draft-ietf-httpbis-p2-semantics-11" anchor="changes.since.11">
 <t>
-  None yet.
+  Closed issues:
+  <list style="symbols"> 
+    <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/232"/>:
+      "User-Agent guidelines" (relating to the 'User-Agent' header field)
+    </t>
+  </list>
 </t>
 </section>

draft-ietf-httpbis/latest/p7-auth.html

@@ -397 +397 @@
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p7-auth-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2010-10-07">
+      <meta name="dct.issued" scheme="ISO8601" content="2010-10-19">
       <meta name="dct.replaces" content="urn:ietf:rfc:2616">
       <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.">
@@ -428 +428 @@
             </tr>
             <tr>
-               <td class="left">Expires: April 10, 2011</td>
+               <td class="left">Expires: April 22, 2011</td>
                <td class="right">HP</td>
             </tr>
@@ -481 +481 @@
             <tr>
                <td class="left"></td>
-               <td class="right">October 7, 2010</td>
+               <td class="right">October 19, 2010</td>
             </tr>
          </tbody>
@@ -507 +507 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on April 10, 2011.</p>
+      <p>This Internet-Draft will expire on April 22, 2011.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>