In article <[EMAIL PROTECTED]> , [EMAIL PROTECTED] (Fgôk ŞôündÉö) wrote:
>In php.ini, upload_max_filesize = 8MB. >When I try to upload file over 5MB, my php file didn't work correctly. >I mean post variable in the php file are lost, session variables also are >lost ... Are you 100% sure that you are looking at the correct php.ini?... What does <?php phpinfo();?> say is the upload_max_filesize? And did you over-ride that with your HTML? There's a tag that can be used to decrease (but not increase) the MAX FILE SIZE. Uploading 5 MB files via HTTP is just a Bad Idea (tm)... Is there any way to move to FTP? I suspect there are several other possible sources of error: Your HTTP server, and any intervening router *IS* allowed to limit the size of a POST to any value they choose, so long as that value is AT LEAST 1 MB. (I think.) While they are all encouraged *NOT* to impose such a limit, they may. The user under which PHP is running *MAY* have some kind of shell limit imposed on their individual temp files or somesuch, I guess... I mean, I know there are things like 'ulimit' and 'usage' and so on (see 'man ulimit') and I reckon somebody somewhere may be bright enough to have come up with a limitation scheme for the 'nobody' user in the '/tmp' directories... I dunno exactly how they might have done that, but it's in the realm of "possible". Client configuration -- There may be a buffer and/or Ethernet communication error that only manifests when you start getting over your 5 MB threshold... On both your desktop and on the web-server, do: ifconfig -a (I think that's ifconfig /a under Winblows... Or, no, ipconfig /a No, that's not right... Hell, I don't know. Go ask Bill!) Anyway, if you do this right before/during/after your upload, and the "Collision Rate" or "errors" or "overruns" or anything that looks like some kind of an "error" increases significantly, your Ethernet settings are probably "wrong" -- They could be "wrong" in a very subtle way involving TTL, MTU, and other TLA's that I don't really understand, and few people do, since everybody who tries to 'splain it to me just confuses me. (So, by definition, they must not understand it very well, eh? :-) You may need to do: whereis ifconfig just to find out where the heck the program lives... If it lives in /sbin, you may need to do: /sbin/ifconfig -a to get an answer. If your ISP is smart, you may not be allowed to even *DO* ifconfig on your web-server... If they are that smart, you can maybe assume they have set it up correctly... Maybe. -- Like Music? http://l-i-e.com/artists.htm -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
