Re: Re: PHP 4.0 Bug #4439 Updated: PHP doesn't handle content-transfer-encoding header on form-based file upload

On Mon, 31 Jul 2000, Rasmus Lerdorf wrote: > > > 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 > That does not mean that it is wise to ignore existing standards. At some point in time, the implementations will follow the standard, so PHP should at least be able to understand it. - Sascha