Seems to me that disabling file uploads *specifically* is a potentially valuable feature, so I think it's worth keeping the INI directive. Ignoring the file entries makes the most sense to me. This wouldn't break existing php.ini files, either (though it would change their effect). Now, it may be worthwhile having a directive that disables multipart POSTs as well, but maybe that makes sense as a separate directive and feature. That's my $.02. peace, Nolan "Zeev Suraski" <[EMAIL PROTECTED]> wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > The way PHP works right now is that multipart encoding is rejected if file > uploads are disabled. We should either change the name of the INI > directive to reflect that it really disables multipart POSTs, or ignore the > file entries in a multipart POST. > > Thoughts? > > At 06:08 28/4/2001, [EMAIL PROTECTED] wrote: > >From: [EMAIL PROTECTED] > >Operating system: Windows 2000 Server > >PHP version: 4.0.4pl1 > >PHP Bug Type: Variables related > >Bug description: empty POST variables when file uploads disabled > > > >I'm not sure if this is a bug or a feature, but I came across it while > >thinking that having GET and POST variables together were causing a > >problem. Turns out it was POST variables not being passed when file > >uploads were disabled and the enctype was multipart. Here's my synopsis: <snip> -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
