Changeset 699 for draft-ietf-httpbis/latest

Timestamp:

Sep 26, 2009, 4:42:37 AM (10 years ago)

Author:

julian.reschke@…

Message:

editorial: enhance readability of header introductions

Location:

draft-ietf-httpbis/latest

Files:

• p3-payload.html (modified) (1 diff)
• p3-payload.xml (modified) (1 diff)

draft-ietf-httpbis/latest/p3-payload.html

@@ -1309 +1309 @@
       <div id="rfc.iref.h.8"></div>
       <h2 id="rfc.section.5.8"><a href="#rfc.section.5.8">5.8</a>&nbsp;<a id="header.content-md5" href="#header.content-md5">Content-MD5</a></h2>
-      <p id="rfc.section.5.8.p.1">The "Content-MD5" entity-header field, as defined in <a href="#RFC1864" id="rfc.xref.RFC1864.1"><cite title="The Content-MD5 Header Field">[RFC1864]</cite></a>, is an MD5 digest of the entity-body for the purpose of providing an end-to-end message integrity check (MIC) of the entity-body.
-         (Note: a MIC is good for detecting accidental modification of the entity-body in transit, but is not proof against malicious
-         attacks.)
+      <p id="rfc.section.5.8.p.1">The "Content-MD5" entity-header field, as defined in <a href="#RFC1864" id="rfc.xref.RFC1864.1"><cite title="The Content-MD5 Header Field">[RFC1864]</cite></a>, is an MD5 digest of the entity-body that provides an end-to-end message integrity check (MIC) of the entity-body. Note that
+         a MIC is good for detecting accidental modification of the entity-body in transit, but is not proof against malicious attacks.
       </p>
       <div id="rfc.figure.u.32"></div><pre class="inline"><span id="rfc.iref.g.33"></span><span id="rfc.iref.g.34"></span>  <a href="#header.content-md5" class="smpl">Content-MD5</a>   = "Content-MD5" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-md5" class="smpl">Content-MD5-v</a>

draft-ietf-httpbis/latest/p3-payload.xml

@@ -1495 +1495 @@
 <t>
    The "Content-MD5" entity-header field, as defined in <xref target="RFC1864"/>, is
-   an MD5 digest of the entity-body for the purpose of providing an
-   end-to-end message integrity check (MIC) of the entity-body. (Note: a
-   MIC is good for detecting accidental modification of the entity-body
-   in transit, but is not proof against malicious attacks.)
+   an MD5 digest of the entity-body that provides an end-to-end message
+   integrity check (MIC) of the entity-body. Note that a MIC is good for
+   detecting accidental modification of the entity-body in transit, but is not
+   proof against malicious attacks.
 </t>
 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Content-MD5"/><iref primary="true" item="Grammar" subitem="Content-MD5-v"/>