Req #50692 [Com]: Don't count 0-bytes files towards the max_file_uploads limit

2010-08-03 Thread phazei at gmail dot com
Edit report at http://bugs.php.net/bug.php?id=50692edit=1

 ID: 50692
 Comment by: phazei at gmail dot com
 Reported by:john dot peterson10 at gmail dot com
 Summary:Don't count 0-bytes files towards the
 max_file_uploads limit
 Status: Open
 Type:   Feature/Change Request
 Package:Feature/Change Request
 Operating System:   Windows
 PHP Version:5.2.12
 Block user comment: N

 New Comment:

This is an issue for me as well.





It can't be adjusted with ini_set or in .htaccess :

http://bugs.php.net/bug.php?id=50684


Previous Comments:

[2010-03-12 14:40:20] mariusads at helpedia dot com

Those people with websites showing 40 input boxes could just as easy
increase the value of the limit in the php.ini or pass it on a case by
case basic through .htaccess (if possible, i don't know)



Don't see the point of this...


[2010-01-08 07:42:43] john dot peterson10 at gmail dot com

Description:

Suggestion: Don't count 0-bytes files (that comes from input
type=file elements that don't have any file specified) towards the
max_file_uploads limit. (And don't create a blank temporary file for
them to avoid the problems with file-system overload mentioned in
CVE-2009-4017.)



Reason for suggestion: That way a small limit for max_file_uploads will
cause less website restrictions. For example: I have seen some designs
with lists of 40 or 50 rows where every row has a input type=file
for the sake of the design of the page. But where typically only one or
two files are submitted in a POST because the majority of the input
type=file elements has no file specified. Currently all these designs
will be limited (to for example 20 rows with the default settings)
because even 0-byte files count towards the max_file_uploads limit.



Issues with suggestion: The site will need javascript to control the
rare exception where more than for example 20 input type=file has a
value before submit. But that should not be a big problem.

Reproduce code:
---
HTML POST request with input type=file elements where the value is
blank (no file specified) so that $_FILES[#]['size'] is 0 (and
$_FILES[#]['tmp_name'] is blank).

Expected result:

input type=file elements where no file is specified doesn't count
towards the max_file_uploads limit

Actual result:
--
input type=file elements where no file is specified counts towards
the max_file_uploads limit






-- 
Edit this bug report at http://bugs.php.net/bug.php?id=50692edit=1


Req #50692 [Com]: Don't count 0-bytes files towards the max_file_uploads limit

2010-03-12 Thread mariusads at helpedia dot com
Edit report at http://bugs.php.net/bug.php?id=50692edit=1

 ID:   50692
 Comment by:   mariusads at helpedia dot com
 Reported by:  john dot peterson10 at gmail dot com
 Summary:  Don't count 0-bytes files towards the max_file_uploads
   limit
 Status:   Open
 Type: Feature/Change Request
 Package:  Feature/Change Request
 Operating System: Windows
 PHP Version:  5.2.12

 New Comment:

Those people with websites showing 40 input boxes could just as easy
increase the value of the limit in the php.ini or pass it on a case by
case basic through .htaccess (if possible, i don't know)



Don't see the point of this...


Previous Comments:

[2010-01-08 07:42:43] john dot peterson10 at gmail dot com

Description:

Suggestion: Don't count 0-bytes files (that comes from input
type=file elements that don't have any file specified) towards the
max_file_uploads limit. (And don't create a blank temporary file for
them to avoid the problems with file-system overload mentioned in
CVE-2009-4017.)



Reason for suggestion: That way a small limit for max_file_uploads will
cause less website restrictions. For example: I have seen some designs
with lists of 40 or 50 rows where every row has a input type=file
for the sake of the design of the page. But where typically only one or
two files are submitted in a POST because the majority of the input
type=file elements has no file specified. Currently all these designs
will be limited (to for example 20 rows with the default settings)
because even 0-byte files count towards the max_file_uploads limit.



Issues with suggestion: The site will need javascript to control the
rare exception where more than for example 20 input type=file has a
value before submit. But that should not be a big problem.

Reproduce code:
---
HTML POST request with input type=file elements where the value is
blank (no file specified) so that $_FILES[#]['size'] is 0 (and
$_FILES[#]['tmp_name'] is blank).

Expected result:

input type=file elements where no file is specified doesn't count
towards the max_file_uploads limit

Actual result:
--
input type=file elements where no file is specified counts towards
the max_file_uploads limit






-- 
Edit this bug report at http://bugs.php.net/bug.php?id=50692edit=1