Re: Re: PHP 4.0 Bug #4439 Updated: PHP doesn't handle content-transfer-encoding header on form-based file upload
| From: | Rasmus Lerdorf | Date: | Mon, 31 Jul 2000 19:53:17 +0000 |
| Subject: | Re: Re: PHP 4.0 Bug #4439 Updated: PHP doesn't handle content-transfer-encoding header on form-based file upload | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-27102@lists.php.net to get a copy of this message | ||
> > Whatever is sending that is not MIME compliant. Double quotes are not
> > optional in the Content-Disposition header. ie. it should be:
> >
> > Content-Disposition: form-data; name="input"
>
> According to RFC 2183 "The Content-Disposition Header Field,"
> specifying the filename should look like:
>
> Content-Disposition: form-data; filename=some.jpeg
>
> The BNF in chapter 2 does not use quoted-string for the
> filename parameter. It also restricts the filename parameter
> to US-ASCII (see 2.3 "The Filename Parameter").
Well, both Netscape and IE went by RFC 1867 when they wrote their file
upload support and RFC-1867 explicitly shows the name (not
filename) argument as being a quoted string.
-Rasmus