PHP Security: Limit Resources Used By Script

by on February 7, 2010 · 6 comments· LAST UPDATED February 7, 2010


How do I control and put limits on php scripts such as maximum execution time of each script and upload file size?

PHP supports the following resource limits directives in php.ini file:

  1. max_execution_time : Maximum execution time of each script, in seconds.
  2. max_input_time : Maximum amount of time each script may spend parsing request data.
  3. memory_limit : Maximum amount of memory a script may consume.

Edit php.ini, enter:
# vi /etc/php.ini
Set up values as follows:

max_execution_time =  30
max_input_time = 30
memory_limit = 40M

Set maximum size of POST data that PHP will accept:

post_max_size = 8M

Set maximum allowed size for uploaded files:

upload_max_filesize = 2M

Turn on or off HTTP file uploads (disallow uploading unless necessary):

file_uploads = Off

Make sure PHP redirects appropriately with the following:

cgi.force_redirect = 0

Disable file requests as fopen calls with the following

allow_url_fopen = Off

Turn on SQL safe mode:

sql.safe_mode = O

Reload Apache web server:
# service httpd reload
Reload lighttpd web server:
# /etc/init.d/lighttpd reload
Note any attempt to exceed these limits will result in a "500 Server Error".

Tweet itFacebook itG+ itDownload PDF versionFound an error/typo on this page?

{ 6 comments… read them below or add one }

1 Roy Kaldung February 8, 2010 at 7:20 pm

The most of these settings can be restricted to specific VirtualHosts. For details
see and


2 Juan Giordana February 9, 2010 at 6:27 am

You don’t need to reload lighty, you need to reload php-cgi or php-fpm.


3 nixCraft February 9, 2010 at 8:07 am


When you reload Lighttpd it reload php-fastcgi too.


4 Nilesh February 9, 2010 at 5:12 pm

@vivek, do you personally use ‘vi’ to edit files ???? vi sucks. vim rocks.

BTW, isn’t this very basic ? Somebody who reads the manual well b4 setup, knows this. But its funny that there are ppl who don’t do that LOL.

@others, you may also be interested in this -Apache2, PHP, mod_fastcgi and SuExec


5 nixCraft February 9, 2010 at 5:17 pm

@Nilesh: vi is aliased to vim. On production server I do not install vim and just use whatever is shipped with distro. Less is better :)


6 Nilesh February 10, 2010 at 8:17 am

@vivek, vi is ok for editing simple config files. but its WORST for editing config files like those of apache. vi cannot highlight whereas vim can.

vi is not always symlinked to vim. in my system (Arch) its linked to ex. and it sucks to core.
I’ve removed it, and set $EDITOR globally to vim. even on my VPS I use vim instead of vi. :)

BTW, where’s the global comment feed ?


Leave a Comment

Tagged as: , , , , , , , , , , , , , , , , , , , , , , , ,

Previous Faq:

Next Faq: