File-upload errors uitgelegd
A responce to admin at creationfarm dot com, Mac OS X and Windows running on a NTFS disk also uses a multi stream file system. Still only the data stream in transfared on http upload. It is preferable to pack Mac OS X files in .dmg files rathere then zip but the avarage user will find zip much easir and they are supported on more platforms.
Standaard valkuilen
Het veld MAX_FILE_SIZE kan geen grotere bestandsgrootte opgeven dan de maximale grootte die is aangegeven met upload_max_filesize in php.ini of met het php_upload_max_filesize Apache .conf directive. Standaard is de maximale grootte 2 Megabytes.
Als memory_limit is ingesteld, is het mogelijk dat een grotere limit nodig is. Wees er dus absoluut zeker van dat deze groot genoeg is!
Als max_execution_time te klein is ingesteld, kan het voorkomen dat je script deze waarde snel overstijgt, wees dus zeker van het feit dat deze groot genoeg is, of zet de maximum bestandsgrootte lager.
Als post_max_size te laag is ingesteld, kunnen er geen grote bestanden worden geupload via de POST methode.
Als je niet controleert of je op het juiste bestand bewerkingen uitvoert, kunnen gebruikers hiervan misbruik maken en gevoelige informatie in andere directories benaderen.
Let op: CERN httpd haalt alles voor de eerste spatie weg in de content-type mime header die gestuurd word door de gebruiker. Zolang CERN httpd dit doet ondersteunt PHP voor deze server niet de bestands-upload mogelijkheid.
Door de vele verschillen in hoe verschillende besturingssystemen werken, kan PHP niet garanderen dat bestanden met exotische name (bijv. met spaties), juist worden herkend, en bewerkt.
add a note
User Contributed NotesStandaard valkuilen
anders jenbo pc dk
02-Oct-2007 12:22
02-Oct-2007 12:22
oliver dot schmidt at drehsinn dot de
09-Dec-2006 07:02
09-Dec-2006 07:02
If you want to use open_basedir for securing your server (which is highly recommended!!!) remember to add your tmp dir to the open_basedir value in php.ini.
Example: open_basedir = <your htdocs root, etc...>:/tmp
(Tested on gentoo Linux, Apache 2.2, PHP 5.1.6)
rbemrose at gmail dot com
20-Dec-2005 10:07
20-Dec-2005 10:07
tjaart:
The HTTP/1.1 standard, section 4.2 says this about message headers:
"Each header field consists of a name followed by a colon (":") and the field value. Field names are case-insensitive. The field value MAY be preceded by any amount of LWS, though a single SP is preferred."
This can be interpreted in two ways:
1. You have to have at least one whitespace character between the header name and field value.
or
2. You can have no whitespace before the field value.
Either way, the standard recommends 1 space, and you already know that works...
tjaart at siam-data-services dot com
22-May-2005 10:27
22-May-2005 10:27
Took me a while to figure this one out...
I think this is actually a header problem, but it only
happens when doing a file upload.
If you attept a header("location:http://...) redirect after
processing a $_POST[''] from a form doing a file upload
(i.e. having enctype="multipart/form-data"), the redirect
doesn't work in IE if you don't have a space between
location: & http, i.e.
header("location:http://...) vs
header("location: http://...)
===================================
<?php
if ($_POST['submit']=='Upload') {
// Process File and the redirect...
header("location: http://"..."/somewhere.php");
exit;
}
?>
<html><head></head><body>
<form enctype="multipart/form-data" action="upload.php" method="POST">
<input type="hidden" name="MAX_FILE_SIZE" value="20000">
Your file: <input name="filename" type="file">
<input name="submit" type="submit" value="Upload">
</form>
</body></html>
===================================
This only happens if all of the following are true:
header("location:http://...) with no space
Form being processed has enctype="multipart/form-data"
Browser=IE
To fix the problem, simply add the space.
Hope this helps someone else.
amalcon _a_t_ eudoramail _d_o_t_ com
11-Aug-2004 11:35
11-Aug-2004 11:35
Note that, when you want to upload VERY large files (or you want to set the limiters VERY high for test purposes), all of the upload file size limiters are stored in signed 32-bit ints. This means that setting a limit higher than about 2.1 GB will result in PHP seeing a large negative number. I have not found any way around this.
morganaj at coleggwent dot ac dot uk
21-Oct-2003 06:53
21-Oct-2003 06:53
Here is another that may make your upload fall over. If you are using Squid or similar proxy server make sure that this is not limiting the size of the HTTP headers. This took me weeks to figure out!
tomcashman at unitekgroup dot com
09-Jun-2003 03:59
09-Jun-2003 03:59
For apache, also check the LimitRequestBody directive.
If you're running a Red Hat install, this might be set in /etc/httpd/conf.d/php.conf.
By default, mine was set to 512 KB.
sebastian at drozdz dot ch
28-Apr-2003 12:59
28-Apr-2003 12:59
It's important that the variable 'open_basedir' in php.ini isn't set to a directory that doesn't not includes tempupload directory
admin at creationfarm dot com
04-Feb-2003 05:16
04-Feb-2003 05:16
The macintosh OS (not sure about OSx) uses a dual forked file system, unlike the rest of the world ;-). Every macintosh file has a data fork and a resource fork. When a dual forked file hits a single forked file system, something has to go, and it is the resource fork. This was recognized as a problem (bad idea to begin with) and apple started recomending that developers avoid sticking vital file info in the resource fork portion of a file, but some files are still very sensitive to this. The main ones to watch out for are macintosh font files and executables, once the resource fork is gone from a mac font or an executable it is useless. To protect the files they should be stuffed or zipped prior to upload to protect the resource fork.
Most mac ftp clients (like fetch) allow files to be uploaded in Macbinhex, which will also protect the resource fork when transfering files via ftp. I have not seen this equivilent in any mac browser (but I haven't done too much digging either).
FYI, apple does have an old utility called ResEdit that lets you manipulate the resource fork portion of a file.