Changeset 1116 for draft-ietf-httpbis-content-disp

Timestamp:

Feb 11, 2011, 9:16:05 AM (9 years ago)

Author:

julian.reschke@…

Message:

say what path separators are (see #272)

Location:

draft-ietf-httpbis-content-disp/latest

Files:

• draft-ietf-httpbis-content-disp.html (modified) (7 diffs)
• draft-ietf-httpbis-content-disp.xml (modified) (2 diffs)

draft-ietf-httpbis-content-disp/latest/draft-ietf-httpbis-content-disp.html

@@ -365 +365 @@
   } 
   @bottom-center {
-       content: "Expires August 14, 2011"; 
+       content: "Expires August 15, 2011"; 
   } 
   @bottom-right {
@@ -405 +405 @@
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-content-disp-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2011-02-10">
+      <meta name="dct.issued" scheme="ISO8601" content="2011-02-11">
       <meta name="dct.abstract" content="HTTP/1.1 defines the Content-Disposition response header field, but points out that it is not part of the HTTP/1.1 Standard. This specification takes over the definition and registration of Content-Disposition, as used in HTTP, and clarifies internationalization aspects.">
       <meta name="description" content="HTTP/1.1 defines the Content-Disposition response header field, but points out that it is not part of the HTTP/1.1 Standard. This specification takes over the definition and registration of Content-Disposition, as used in HTTP, and clarifies internationalization aspects.">
@@ -423 +423 @@
                <td class="left">Updates: <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved)
                </td>
-               <td class="right">February 10, 2011</td>
+               <td class="right">February 11, 2011</td>
             </tr>
             <tr>
@@ -430 +430 @@
             </tr>
             <tr>
-               <td class="left">Expires: August 14, 2011</td>
+               <td class="left">Expires: August 15, 2011</td>
                <td class="right"></td>
             </tr>
@@ -459 +459 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on August 14, 2011.</p>
+      <p>This Internet-Draft will expire on August 15, 2011.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
@@ -620 +620 @@
       <ul>
          <li>
-            <p>When the value contains path separator characters, recipients <em class="bcp14">SHOULD</em> ignore all but the last path segment. This prevents unintentional overwriting of well-known file system location (such as
+            <p>When the value contains path separator characters ("\" or "/"), recipients <em class="bcp14">SHOULD</em> ignore all but the last path segment. This prevents unintentional overwriting of well-known file system locations (such as
                "/etc/passwd").
             </p>
@@ -959 +959 @@
       <p id="rfc.section.D.9.p.1">Updated implementation information (Chrome 9 implements RFC 5987).</p>
       <p id="rfc.section.D.9.p.2">Clarify who requirements are on, add a section discussing conformance and handling of invalid field values in general.</p>
+      <p id="rfc.section.D.9.p.3">Closed issues: </p>
+      <ul>
+         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/272">http://tools.ietf.org/wg/httpbis/trac/ticket/272</a>&gt;: "Path Separator Characters"
+         </li>
+      </ul>
       <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
       <p class="noprint"><a href="#rfc.index.C">C</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.R">R</a> 

draft-ietf-httpbis-content-disp/latest/draft-ietf-httpbis-content-disp.xml

@@ -250 +250 @@
   <list style="symbols">
     <x:lt><t>
-      When the value contains path separator characters, recipients &SHOULD;
-      ignore all but the last path segment. This prevents unintentional
-      overwriting of well-known file system location (such as "/etc/passwd").
+      When the value contains path separator characters ("\" or "/"),
+      recipients &SHOULD; ignore all but the last path segment. This prevents
+      unintentional overwriting of well-known file system locations (such as
+      "/etc/passwd").
     </t></x:lt>
     <x:lt><t>
@@ -952 +953 @@
   and handling of invalid field values in general.
 </t>
+<t>
+  Closed issues:
+  <list style="symbols">
+    <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/272"/>:
+      "Path Separator Characters"
+    </t>
+  </list>
+</t>
 </section>