[html5] r6206 - [giow] (2) Add requirements for how to express file names in formdata Fixing htt [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2011-06-09 11:18:02 -0700 (Thu, 09 Jun 2011)
New Revision: 6206

Modified:
   complete.html
   index
   source
Log:
[giow] (2) Add requirements for how to express file names in formdata
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=11452

Modified: complete.html
===================================================================
--- complete.html	2011-06-09 17:07:45 UTC (rev 6205)
+++ complete.html	2011-06-09 18:18:02 UTC (rev 6206)
@@ -52265,6 +52265,16 @@
     not get converted to a 7-bit safe encoding as suggested in RFC
     2388).</p>
 
+    <p>File names included in the generated <code title="">multipart/form-data</code> resource (as part of file
+    fields) must use the character encoding selected above, though the
+    precise name may be approximated if necessary (e.g. newlines could
+    be removed from file names, quotes could be changed to "%22", and
+    characters not expressible in the selected character encoding
+    could be replaced by other characters). User agents must not use
+    the RFC 2231 encoding suggested by RFC 2388.</p> <!-- this isn't a
+    willful violation since 2388 doesn't make it a requirement, it
+    just vaguely suggests it -->
+
     <p>The boundary used by the user agent in generating the return
     value of this algorithm is the <dfn id=multipart/form-data-boundary-string><code title="">multipart/form-data</code> boundary string</dfn>. (This
     value is used to generate the MIME type of the form submission

Modified: index
===================================================================
--- index	2011-06-09 17:07:45 UTC (rev 6205)
+++ index	2011-06-09 18:18:02 UTC (rev 6206)
@@ -52258,6 +52258,16 @@
     not get converted to a 7-bit safe encoding as suggested in RFC
     2388).</p>
 
+    <p>File names included in the generated <code title="">multipart/form-data</code> resource (as part of file
+    fields) must use the character encoding selected above, though the
+    precise name may be approximated if necessary (e.g. newlines could
+    be removed from file names, quotes could be changed to "%22", and
+    characters not expressible in the selected character encoding
+    could be replaced by other characters). User agents must not use
+    the RFC 2231 encoding suggested by RFC 2388.</p> <!-- this isn't a
+    willful violation since 2388 doesn't make it a requirement, it
+    just vaguely suggests it -->
+
     <p>The boundary used by the user agent in generating the return
     value of this algorithm is the <dfn id=multipart/form-data-boundary-string><code title="">multipart/form-data</code> boundary string</dfn>. (This
     value is used to generate the MIME type of the form submission

Modified: source
===================================================================
--- source	2011-06-09 17:07:45 UTC (rev 6205)
+++ source	2011-06-09 18:18:02 UTC (rev 6206)
@@ -59037,6 +59037,17 @@
     not get converted to a 7-bit safe encoding as suggested in RFC
     2388).</p>
 
+    <p>File names included in the generated <code
+    title="">multipart/form-data</code> resource (as part of file
+    fields) must use the character encoding selected above, though the
+    precise name may be approximated if necessary (e.g. newlines could
+    be removed from file names, quotes could be changed to "%22", and
+    characters not expressible in the selected character encoding
+    could be replaced by other characters). User agents must not use
+    the RFC 2231 encoding suggested by RFC 2388.</p> <!-- this isn't a
+    willful violation since 2388 doesn't make it a requirement, it
+    just vaguely suggests it -->
+
     <p>The boundary used by the user agent in generating the return
     value of this algorithm is the <dfn><code
     title="">multipart/form-data</code> boundary string</dfn>. (This