Changeset 1308

Timestamp:

Jun 10, 2011, 12:32:29 AM (9 years ago)

Author:

julian.reschke@…

Message:

remove TAB characters (not even editorial)

File:

• draft-ietf-httpbis/latest/p3-payload.xml (modified) (5 diffs)

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

@@ -2286 +2286 @@
     <author initials="L." surname="Chen" fullname="L. Chen"/>
     <date year="2011" month="March" />
-        </front>
+  </front>
   <seriesInfo name="RFC" value="6151" />
 </reference>
@@ -2311 +2311 @@
 
 <reference anchor="RFC6266">
-        <front>
+  <front>
     <title abbrev="Content-Disposition in HTTP">Use of the Content-Disposition Header Field
     in the Hypertext Transfer Protocol (HTTP)</title>
@@ -2317 +2317 @@
       <organization abbrev="greenbytes">greenbytes GmbH</organization>
       <address>
-        <email>julian.reschke@greenbytes.de</email>     
+        <email>julian.reschke@greenbytes.de</email>
       </address>
     </author>
@@ -2500 +2500 @@
 </t>
 <t>
-        Remove definition of Content-MD5 header field because it was inconsistently
-        implemented with respect to partial responses, and also because of known
-        deficiencies in the hash algorithm itself (see <xref target="RFC6151"/> for details).
+  Remove definition of Content-MD5 header field because it was inconsistently
+  implemented with respect to partial responses, and also because of known
+  deficiencies in the hash algorithm itself (see <xref target="RFC6151"/> for details).
   (<xref target="header.fields"/>)
 </t>
@@ -2517 +2517 @@
 </t>
 <t>
-        Remove discussion of Content-Disposition header field, it is now defined
-        by <xref target="RFC6266"/>.
+  Remove discussion of Content-Disposition header field, it is now defined
+  by <xref target="RFC6266"/>.
   (<xref target="additional.features"/>)
 </t>