Maybe the post_max_size is also exceeded, and therefore it's handled with sense I think.. Otherwise I'm not sure I think this is handled the right way, if it's only upload_max_filesize that's exceeded.
-- // DvDmanDT MSN: dvdmandt€hotmail.com Mail: dvdmandt€telia.com "John W. Holmes" <[EMAIL PROTECTED]> skrev i meddelandet news:[EMAIL PROTECTED] > From: "Jay Blanchard" <[EMAIL PROTECTED]> > > > [snip] > > > I have a form in a page 1, that POSTs a file and some hidden's to page > > > 2. If > > > the file size is bigger that the max in php.ini, in page 2, $_POST is > > > empty. > > > [/snip] > > > > Why, of course it is! The php.ini sets the max file size $_POST will be > > empty because it would not be allowed to load. You have two choices; > > > > A. increase the max file size in the php.ini > > 2. reduce the size of the file being uploaded. > > > > It is not a bug. > > I understand what you're saying, and maybe the OP will agree with me here, > but does that seem like the natural way for it to be handled? Shouldn't > $_FILES be empty and $_POST still have the rest of the posted data? PHP > decides to reject the file, but why does it reject the rest of the post > data, also? > > Maybe off-topic for this list, but if that's what the OP was talking about, > then I've got to kind of agree with him. > > ---John Holmes... -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
