Changeset 1036 for draft-ietf-httpbis/latest/p2-semantics.xml

Timestamp:

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

Author:

julian.reschke@…

Message:

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

File:

• draft-ietf-httpbis/latest/p2-semantics.xml (modified) (3 diffs)

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>