PHP 7.4.0beta4 released!

## Description of core php.ini directives

This list includes the core php.ini directives you can set to configure your PHP setup. Directives handled by extensions are listed and detailed at the extension documentation pages respectively; Information on the session directives for example can be found at the sessions page.

Note:

The defaults listed here are used when php.ini is not loaded; the values for the production and development php.ini may vary.

## Language Options

Language and Misc Configuration Options
Name Default Changeable Changelog
short_open_tag "1" PHP_INI_PERDIR
asp_tags "0" PHP_INI_PERDIR Removed in PHP 7.0.0.
precision "14" PHP_INI_ALL
serialize_precision "-1" PHP_INI_ALL Before PHP 5.3.6, the default value was 100. Before PHP 7.1.0, the default value was 17.
y2k_compliance "1" PHP_INI_ALL Removed in PHP 5.4.0.
allow_call_time_pass_reference "1" PHP_INI_PERDIR Removed in PHP 5.4.0.
disable_functions "" PHP_INI_SYSTEM only
disable_classes "" php.ini only
exit_on_timeout "" PHP_INI_ALL Available since PHP 5.3.0.
expose_php "1" php.ini only
hard_timeout "2" PHP_INI_SYSTEM Available since PHP 7.1.0.
zend.multibyte "0" PHP_INI_ALL Available since PHP 5.4.0
zend.script_encoding NULL PHP_INI_ALL Available since PHP 5.4.0
zend.detect-unicode NULL PHP_INI_ALL Available since PHP 5.4.0
zend.signal_check "0" PHP_INI_SYSTEM Available since PHP 5.4.0
zend.assertions "1" PHP_INI_ALL with restrictions Available since PHP 7.0.0.
zend.ze1_compatibility_mode "0" PHP_INI_ALL Removed in PHP 5.3.0
detect_unicode "1" PHP_INI_ALL Available since PHP 5.1.0. Renamed to zend.detect-unicode from PHP 5.4.0.

Here's a short explanation of the configuration directives.

short_open_tag boolean

Tells PHP whether the short form (<? ?>) of PHP's open tag should be allowed. If you want to use PHP in combination with XML, you can disable this option in order to use <?xml ?> inline. Otherwise, you can print it with PHP, for example: <?php echo '<?xml version="1.0"?>'; ?>. Also, if disabled, you must use the long form of the PHP open tag (<?php ?>).

Note:

This directive also affected the shorthand <?= before PHP 5.4.0, which is identical to <? echo. Use of this shortcut required short_open_tag to be on. Since PHP 5.4.0, <?= is always available.

asp_tags boolean
Enables the use of ASP-like <% %> tags in addition to the usual <?php ?> tags. This includes the variable-value printing shorthand of <%= $value %>. For more information, see Escaping from HTML. Changelog for asp_tags Version Description 7.0.0 Removed from PHP. precision integer The number of significant digits displayed in floating point numbers. -1 means that an enhanced algorithm for rounding such numbers will be used. serialize_precision integer The number of significant digits stored while serializing floating point numbers. -1 means that an enhanced algorithm for rounding such numbers will be used. y2k_compliance boolean Enforce year 2000 compliance (will cause problems with non-compliant browsers) allow_call_time_pass_reference boolean Whether to warn when arguments are passed by reference at function call time. The encouraged method of specifying which arguments should be passed by reference is in the function declaration. You're encouraged to try and turn this option Off and make sure your scripts work properly with it in order to ensure they will work with future versions of the language (you will receive a warning each time you use this feature). Passing arguments by reference at function call time was deprecated for code-cleanliness reasons. A function can modify its arguments in an undocumented way if it didn't declare that the argument shall be passed by reference. To prevent side-effects it's better to specify which arguments are passed by reference in the function declaration only. See also References Explained. Changelog for allow_call_time_pass_reference Version Description 5.4.0 Removed from PHP. 5.3.0 Emits an E_DEPRECATED level error. 5.0.0 Deprecated, and generates an E_COMPILE_WARNING level error. expose_php boolean Exposes to the world that PHP is installed on the server, which includes the PHP version within the HTTP header (e.g., X-Powered-By: PHP/5.3.7). Prior to PHP 5.5.0 the PHP logo guids are also exposed, thus appending them to the URL of your PHP script would display the appropriate logo (e.g., » https://www.php.net/?=PHPE9568F34-D428-11d2-A769-00AA001ACF42). This also affected the output of phpinfo(), as when disabled, the PHP logo and credits information would not be displayed. Note: Since PHP 5.5.0 these guids and the php_logo_guid() function have been removed from PHP and the guids are replaced with data URIs instead. Thus accessing the PHP logo via appending the guid to the URL no longer works. Similarly, turning expose_php off will not affect seeing the PHP logo in phpinfo(). See also php_logo_guid() and phpcredits(). disable_functions string This directive allows you to disable certain functions for security reasons. It takes on a comma-delimited list of function names. disable_functions is not affected by Safe Mode. Only internal functions can be disabled using this directive. User-defined functions are unaffected. This directive must be set in php.ini For example, you cannot set this in httpd.conf. disable_classes string This directive allows you to disable certain classes for security reasons. It takes on a comma-delimited list of class names. disable_classes is not affected by Safe Mode. This directive must be set in php.ini For example, you cannot set this in httpd.conf. zend.assertions integer When set to 1, assertion code will be generated and executed (development mode). When set to 0, assertion code will be generated but it will be skipped (not executed) at runtime. When set to -1, assertion code will not be generated, making the assertions zero-cost (production mode). Note: If a process is started in production mode, zend.assertions cannot be changed at runtime, since the code for assertions was not generated. If a process is started in development mode, zend.assertions cannot be set to -1 at runtime. zend.ze1_compatibility_mode boolean Enable compatibility mode with Zend Engine 1 (PHP 4). It affects the cloning, casting (objects with no properties cast to FALSE or 0), and comparing of objects. In this mode, objects are passed by value instead of reference by default. See also the section titled Migrating from PHP 4 to PHP 5. Warning This feature has been DEPRECATED and REMOVED as of PHP 5.3.0. hard_timeout integer zend.multibyte boolean Enables parsing of source files in multibyte encodings. Enabling zend.multibyte is required to use character encodings like SJIS, BIG5, etc that contain special characters in multibyte string data. ISO-8859-1 compatible encodings like UTF-8, EUC, etc do not require this option. Enabling zend.multibyte requires the mbstring extension to be available. zend.script_encoding string This value will be used unless a declare(encoding=...) directive appears at the top of the script. When ISO-8859-1 incompatible encoding is used, both zend.multibyte and zend.script_encoding must be used. Literal strings will be transliterated from zend.script_enconding to mbstring.internal_encoding, as if mb_convert_encoding() would have been called. zend.detect_unicode boolean Check for BOM (Byte Order Mark) and see if the file contains valid multibyte characters. This detection is performed before processing of __halt_compiler(). Available only in Zend Multibyte mode. zend.signal_check boolean To check for replaced signal handlers on shutdown. exit_on_timeout boolean This is an Apache1 mod_php-only directive that forces an Apache child to exit if a PHP execution timeout occurred. Such a timeout causes an internal longjmp() call in Apache1 which can leave some extensions in an inconsistent state. By terminating the process any outstanding locks or memory will be cleaned up. ## Resource Limits Resource Limits Name Default Changeable Changelog memory_limit "128M" PHP_INI_ALL "8M" before PHP 5.2.0, "16M" in PHP 5.2.0 Here's a short explanation of the configuration directives. memory_limit integer This sets the maximum amount of memory in bytes that a script is allowed to allocate. This helps prevent poorly written scripts for eating up all available memory on a server. Note that to have no memory limit, set this directive to -1. Prior to PHP 5.2.1, in order to use this directive it had to be enabled at compile time by using --enable-memory-limit in the configure line. This compile-time flag was also required to define the functions memory_get_usage() and memory_get_peak_usage() prior to 5.2.1. When an integer is used, the value is measured in bytes. Shorthand notation, as described in this FAQ, may also be used. See also: max_execution_time. ## Performance Tuning Performance Tuning Name Default Changeable Changelog realpath_cache_size "4M" PHP_INI_SYSTEM Available since PHP 5.1.0. Prior to PHP 7.0.16 and 7.1.2, the default was "16K" realpath_cache_ttl "120" PHP_INI_SYSTEM Available since PHP 5.1.0. Note: Using open_basedir will disable the realpath cache. Here's a short explanation of the configuration directives. realpath_cache_size integer Determines the size of the realpath cache to be used by PHP. This value should be increased on systems where PHP opens many files, to reflect the quantity of the file operations performed. The size represents the total number of bytes in the path strings stored, plus the size of the data associated with the cache entry. This means that in order to store longer paths in the cache, the cache size must be larger. This value does not directly control the number of distinct paths that can be cached. The size required for the cache entry data is system dependent. realpath_cache_ttl integer Duration of time (in seconds) for which to cache realpath information for a given file or directory. For systems with rarely changing files, consider increasing the value. ## Data Handling Data Handling Configuration Options Name Default Changeable Changelog arg_separator.output "&" PHP_INI_ALL arg_separator.input "&" PHP_INI_PERDIR variables_order "EGPCS" PHP_INI_PERDIR PHP_INI_ALL in PHP <= 5.0.5. request_order "" PHP_INI_PERDIR Available since PHP 5.3.0 auto_globals_jit "1" PHP_INI_PERDIR Available since PHP 5.0.0. register_globals "0" PHP_INI_PERDIR Removed in PHP 5.4.0. register_argc_argv "1" PHP_INI_PERDIR register_long_arrays "1" PHP_INI_PERDIR Deprecated in PHP 5.3.0. Removed in PHP 5.4.0. enable_post_data_reading "1" PHP_INI_PERDIR Available since PHP 5.4.0 post_max_size "8M" PHP_INI_PERDIR auto_prepend_file NULL PHP_INI_PERDIR auto_append_file NULL PHP_INI_PERDIR default_mimetype "text/html" PHP_INI_ALL default_charset "UTF-8" PHP_INI_ALL Defaults to "UTF-8" since PHP >= 5.6.0; empty for PHP < 5.6.0. always_populate_raw_post_data "0" PHP_INI_PERDIR Removed in PHP 7.0.0. Here's a short explanation of the configuration directives. arg_separator.output string The separator used in PHP generated URLs to separate arguments. arg_separator.input string List of separator(s) used by PHP to parse input URLs into variables. Note: Every character in this directive is considered as separator! variables_order string Sets the order of the EGPCS (Environment, Get, Post, Cookie, and Server) variable parsing. For example, if variables_order is set to "SP" then PHP will create the superglobals$_SERVER and $_POST, but not create$_ENV, $_GET, and$_COOKIE. Setting to "" means no superglobals will be set.

If the deprecated register_globals directive is on, then variables_order also configures the order the ENV, GET, POST, COOKIE and SERVER variables are populated in global scope. So for example if variables_order is set to "EGPCS", register_globals is enabled, and both $_GET['action'] and$_POST['action'] are set, then $action will contain the value of$_POST['action'] as P comes after G in our example directive value.

Warning

In both the CGI and FastCGI SAPIs, $_SERVER is also populated by values from the environment; S is always equivalent to ES regardless of the placement of E elsewhere in this directive. Note: The content and order of$_REQUEST is also affected by this directive.

request_order string

This directive describes the order in which PHP registers GET, POST and Cookie variables into the _REQUEST array. Registration is done from left to right, newer values override older values.

If this directive is not set, variables_order is used for $_REQUEST contents. Note that the default distribution php.ini files does not contain the 'C' for cookies, due to security concerns. auto_globals_jit boolean When enabled, the SERVER, REQUEST, and ENV variables are created when they're first used (Just In Time) instead of when the script starts. If these variables are not used within a script, having this directive on will result in a performance gain. The PHP directives register_globals, register_long_arrays, and register_argc_argv must be disabled for this directive to have any affect. Since PHP 5.1.3 it is not necessary to have register_argc_argv disabled. Warning Usage of SERVER, REQUEST, and ENV variables is checked during the compile time so using them through e.g. variable variables will not cause their initialization. register_globals boolean Whether or not to register the EGPCS (Environment, GET, POST, Cookie, Server) variables as global variables. As of » PHP 4.2.0, this directive defaults to off. Please read the security chapter on Using register_globals for related information. Please note that register_globals cannot be set at runtime (ini_set()). Although, you can use .htaccess if your host allows it as described above. An example .htaccess entry: php_flag register_globals off. Note: register_globals is affected by the variables_order directive. Warning This feature has been DEPRECATED as of PHP 5.3.0 and REMOVED as of PHP 5.4.0. register_argc_argv boolean Tells PHP whether to declare the argv & argc variables (that would contain the GET information). See also command line. register_long_arrays boolean Tells PHP whether or not to register the deprecated long$HTTP_*_VARS type predefined variables. When On (default), long predefined PHP variables like $HTTP_GET_VARS will be defined. If you're not using them, it's recommended to turn them off, for performance reasons. Instead, use the superglobal arrays, like$_GET. This directive became available in PHP 5.0.0.
Warning

This feature has been DEPRECATED as of PHP 5.3.0 and REMOVED as of PHP 5.4.0.

enable_post_data_reading boolean
Disabling this option causes $_POST and$_FILES not to be populated. The only way to read postdata will then be through the php://input stream wrapper. This can be useful to proxy requests or to process the POST data in a memory efficient fashion.
post_max_size integer
Sets max size of post data allowed. This setting also affects file upload. To upload large files, this value must be larger than upload_max_filesize. Generally speaking, memory_limit should be larger than post_max_size. When an integer is used, the value is measured in bytes. Shorthand notation, as described in this FAQ, may also be used. If the size of post data is greater than post_max_size, the $_POST and$_FILES superglobals are empty. This can be tracked in various ways, e.g. by passing the $_GET variable to the script processing the data, i.e. <form action="edit.php?processed=1">, and then checking if$_GET['processed'] is set.

Note:

PHP allows shortcuts for byte values, including K (kilo), M (mega) and G (giga). PHP will do the conversions automatically if you use any of these. Be careful not to exceed the 32 bit signed integer limit (if you're using 32bit versions) as it will cause your script to fail.

Changelog for post_max_size
Version Description
5.3.4 post_max_size = 0 will not disable the limit when the content type is application/x-www-form-urlencoded or is not registered with PHP.
5.3.2 , 5.2.12 Allow unlimited post size by setting post_max_size to 0.

auto_prepend_file string

Specifies the name of a file that is automatically parsed before the main file. The file is included as if it was called with the require function, so include_path is used.

The special value none disables auto-prepending.

auto_append_file string

Specifies the name of a file that is automatically parsed after the main file. The file is included as if it was called with the require function, so include_path is used.

The special value none disables auto-appending.

Note: If the script is terminated with exit(), auto-append will not occur.

default_mimetype string

By default, PHP will output a media type using the Content-Type header. To disable this, simply set it to be empty.

PHP's built-in default media type is set to text/html.

default_charset string

In PHP 5.6 onwards, "UTF-8" is the default value and its value is used as the default character encoding for htmlentities(), html_entity_decode() and htmlspecialchars() if the encoding parameter is omitted. The value of default_charset will also be used to set the default character set for iconv functions if the iconv.input_encoding, iconv.output_encoding and iconv.internal_encoding configuration options are unset, and for mbstring functions if the mbstring.http_input mbstring.http_output mbstring.internal_encoding configuration option is unset.

All versions of PHP will use this value as the charset within the default Content-Type header sent by PHP if the header isn't overridden by a call to header().

Setting default_charset to an empty value is not recommended.

input_encoding string

Available from PHP 5.6.0. This setting is used for multibyte modules such as mbstring and iconv. Default is empty.

output_encoding string

Available from PHP 5.6.0. This setting is used for multibyte modules such as mbstring and iconv. Default is empty.

internal_encoding string

Available from PHP 5.6.0. This setting is used for multibyte modules such as mbstring and iconv. Default is empty. If empty, default_charset is used.

always_populate_raw_post_data mixed
Warning

This feature was DEPRECATED in PHP 5.6.0, and REMOVED as of PHP 7.0.0.

If set to TRUE, PHP will always populate the $HTTP_RAW_POST_DATA containing the raw POST data. Otherwise, the variable is populated only when the MIME type of the data is unrecognised. The preferred method for accessing raw POST data is php://input, and$HTTP_RAW_POST_DATA is deprecated in PHP 5.6.0 onwards. Setting always_populate_raw_post_data to -1 will opt into the new behaviour that will be implemented in a future version of PHP, in which $HTTP_RAW_POST_DATA is never defined. Regardless of the setting,$HTTP_RAW_POST_DATA is not available with enctype="multipart/form-data".

## Paths and Directories

Paths and Directories Configuration Options
Name Default Changeable Changelog
include_path ".;/path/to/php/pear" PHP_INI_ALL
open_basedir NULL PHP_INI_ALL PHP_INI_SYSTEM in PHP < 5.3.0
doc_root NULL PHP_INI_SYSTEM
user_dir NULL PHP_INI_SYSTEM
user_ini.cache_ttl "300" PHP_INI_SYSTEM Available since PHP 5.3.0.
user_ini.filename ".user.ini" PHP_INI_SYSTEM Available since PHP 5.3.0.
extension_dir "/path/to/php" PHP_INI_SYSTEM
extension NULL php.ini only
zend_extension NULL php.ini only
zend_extension_debug NULL php.ini only Available before PHP 5.3.0.
zend_extension_debug_ts NULL php.ini only Available before PHP 5.3.0.
zend_extension_ts NULL php.ini only Available before PHP 5.3.0.
cgi.check_shebang_line "1" PHP_INI_SYSTEM Available since PHP 5.2.0.
cgi.discard_path "0" PHP_INI_SYSTEM Available since PHP 5.3.0.
cgi.fix_pathinfo "1" PHP_INI_SYSTEM PHP_INI_ALL prior to PHP 5.2.1.
cgi.force_redirect "1" PHP_INI_SYSTEM PHP_INI_ALL prior to PHP 5.2.1.
cgi.nph "0" PHP_INI_SYSTEM Available since PHP 5.3.0.
cgi.redirect_status_env NULL PHP_INI_SYSTEM PHP_INI_ALL prior to PHP 5.2.1.
fastcgi.impersonate "0" PHP_INI_SYSTEM PHP_INI_ALL prior to PHP 5.2.1.
fastcgi.logging "1" PHP_INI_SYSTEM PHP_INI_ALL prior to PHP 5.2.1.

Here's a short explanation of the configuration directives.

include_path string

Specifies a list of directories where the require, include, fopen(), file(), readfile() and file_get_contents() functions look for files. The format is like the system's PATH environment variable: a list of directories separated with a colon in Unix or semicolon in Windows.

PHP considers each entry in the include path separately when looking for files to include. It will check the first path, and if it doesn't find it, check the next path, until it either locates the included file or returns with a warning or an error. You may modify or set your include path at runtime using set_include_path().

Example #1 Unix include_path

include_path=".:/php/includes"

Example #2 Windows include_path

include_path=".;c:\php\includes"

Using a . in the include path allows for relative includes as it means the current directory. However, it is more efficient to explicitly use include './file' than having PHP always check the current directory for every include.

Note:

ENV variables are also accessible in .ini files. As such it is possible to reference the home directory using ${LOGIN} and${USER}.

Environment variables may vary between Server APIs as those environments may be different.

Example #3 Unix include_path using ${USER} env variable include_path = ".:${USER}/pear/php"

open_basedir string

Limit the files that can be accessed by PHP to the specified directory-tree, including the file itself. This directive is NOT affected by whether Safe Mode is turned On or Off.

When a script tries to access the filesystem, for example using include, or fopen(), the location of the file is checked. When the file is outside the specified directory-tree, PHP will refuse to access it. All symbolic links are resolved, so it's not possible to avoid this restriction with a symlink. If the file doesn't exist then the symlink couldn't be resolved and the filename is compared to (a resolved) open_basedir .

open_basedir can affect more than just filesystem functions; for example if MySQL is configured to use mysqlnd drivers, LOAD DATA INFILE will be affected by open_basedir . Much of the extended functionality of PHP uses open_basedir in this way.

The special value . indicates that the working directory of the script will be used as the base-directory. This is, however, a little dangerous as the working directory of the script can easily be changed with chdir().

In httpd.conf, open_basedir can be turned off (e.g. for some virtual hosts) the same way as any other configuration directive with "php_admin_value open_basedir none".

Under Windows, separate the directories with a semicolon. On all other systems, separate the directories with a colon. As an Apache module, open_basedir paths from parent directories are now automatically inherited.

The restriction specified with open_basedir is a directory name since PHP 5.2.16 and 5.3.4. Previous versions used it as a prefix. This means that "open_basedir = /dir/incl" also allowed access to "/dir/include" and "/dir/incls" if they exist. When you want to restrict access to only the specified directory, end with a slash. For example: open_basedir = /dir/incl/

The default is to allow all files to be opened.

Note:

As of PHP 5.3.0 open_basedir can be tightened at run-time. This means that if open_basedir is set to /www/ in php.ini a script can tighten the configuration to /www/tmp/ at run-time with ini_set(). When listing several directories, you can use the PATH_SEPARATOR constant as a separator regardless of the operating system.

Note:

Using open_basedir will set realpath_cache_size to 0 and thus disable the realpath cache.

doc_root string

PHP's "root directory" on the server. Only used if non-empty. If PHP is configured with safe mode, no files outside this directory are served. If PHP was not compiled with FORCE_REDIRECT, you should set doc_root if you are running PHP as a CGI under any web server (other than IIS). The alternative is to use the cgi.force_redirect configuration below.

user_ini.cache_ttl integer

user_ini.filename string

user_dir string

The base name of the directory used on a user's home directory for PHP files, for example public_html .

extension_dir string

extension string

zend_extension string

Name of dynamically loadable Zend extension (for example APD) to load when PHP starts up.

zend_extension_debug string

Variant of zend_extension for extensions compiled with debug info prior to PHP 5.3.0.

zend_extension_debug_ts string

Variant of zend_extension for extensions compiled with debug info and thread safety prior to PHP 5.3.0.

zend_extension_ts string

Variant of zend_extension for extensions compiled with thread safety prior to PHP 5.3.0.

cgi.check_shebang_line boolean

Controls whether CGI PHP checks for line starting with #! (shebang) at the top of the running script. This line might be needed if the script support running both as stand-alone script and via PHP CGI. PHP in CGI mode skips this line and ignores its content if this directive is turned on.

cgi.discard_path boolean

If this is enabled, the PHP CGI binary can safely be placed outside of the web tree and people will not be able to circumvent .htaccess security.

cgi.fix_pathinfo boolean

Provides real PATH_INFO/ PATH_TRANSLATED support for CGI. PHP's previous behaviour was to set PATH_TRANSLATED to SCRIPT_FILENAME, and to not grok what PATH_INFO is. For more information on PATH_INFO, see the CGI specs. Setting this to 1 will cause PHP CGI to fix its paths to conform to the spec. A setting of zero causes PHP to behave as before. It is turned on by default. You should fix your scripts to use SCRIPT_FILENAME rather than PATH_TRANSLATED.

cgi.force_redirect boolean

cgi.force_redirect is necessary to provide security running PHP as a CGI under most web servers. Left undefined, PHP turns this on by default. You can turn it off at your own risk.

Note:

Windows Users: When using IIS this option must be turned off. For OmniHTTPD or Xitami the same applies.

cgi.nph boolean

If cgi.nph is enabled it will force cgi to always sent Status: 200 with every request.

cgi.redirect_status_env string

If cgi.force_redirect is turned on, and you are not running under Apache or Netscape (iPlanet) web servers, you may need to set an environment variable name that PHP will look for to know it is OK to continue execution.

Note:

Setting this variable may cause security issues, know what you are doing first.

cgi.rfc2616_headers int

Tells PHP what type of headers to use when sending HTTP response code. If it's set to 0, PHP sends a » RFC 3875 "Status:" header that is supported by Apache and other web servers. When this option is set to 1, PHP will send » RFC 2616 compliant headers.

If this option is enabled, and you are running PHP in a CGI environment (e.g. PHP-FPM) you should not use standard RFC 2616 style HTTP status response headers, you should instead use their RFC 3875 equivalent e.g. instead of header("HTTP/1.0 404 Not found"); you should use header("Status: 404 Not Found");

Leave it set to 0 unless you know what you're doing.

fastcgi.impersonate string

FastCGI under IIS (on WINNT based OS) supports the ability to impersonate security tokens of the calling client. This allows IIS to define the security context that the request runs under. mod_fastcgi under Apache does not currently support this feature (03/17/2002) Set to 1 if running under IIS. Default is zero.

fastcgi.logging boolean

Turns on SAPI logging when using FastCGI. Default is to enable logging.

Name Default Changeable Changelog
max_input_nesting_level 64 PHP_INI_PERDIR Available since PHP 5.3.9.
max_input_vars 1000 PHP_INI_PERDIR Available since PHP 5.3.9.
max_file_uploads 20 PHP_INI_SYSTEM Available since PHP 5.2.12.

Here's a short explanation of the configuration directives.

file_uploads boolean

upload_tmp_dir string

The temporary directory used for storing files when doing file upload. Must be writable by whatever user PHP is running as. If not specified PHP will use the system's default.

If the directory specified here is not writable, PHP falls back to the system default temporary directory. If open_basedir is on, then the system default directory must be allowed for an upload to succeed.

upload_max_filesize integer

The maximum size of an uploaded file.

When an integer is used, the value is measured in bytes. Shorthand notation, as described in this FAQ, may also be used.
max_file_uploads integer

The maximum number of files allowed to be uploaded simultaneously. Starting with PHP 5.3.4, upload fields left blank on submission do not count towards this limit.

## General SQL

General SQL Configuration Options
Name Default Changeable Changelog
sql.safe_mode "0" PHP_INI_SYSTEM Removed in PHP 7.2.0

Here's a short explanation of the configuration directives.

sql.safe_mode boolean

If turned on, database connection functions that specify default values will use those values in place of any user-supplied arguments. For details on the default values, see the documentation for the relevant connection functions.

Warning

This feature has been REMOVED as of PHP 7.2.0.

## Windows Specific

Windows Specific Configuration Options
Name Default Changeable Changelog
windows.show_crt_warning "0" PHP_INI_ALL Available since PHP 5.4.0.

Here's a short explanation of the configuration directives.

windows.show_crt_warning boolean

This directive shows the Windows CRT warnings when enabled. These warnings were displayed by default until PHP 5.4.0.

### User Contributed Notes 16 notes

22
csg at DEL_THISdiatom dot de
13 years ago
 Starting with PHP 4.4.0 (at least PHP version 4.3.10 did have old, documented behaviour) interpretation of value of "session.save_path" did change in conjunction with "save_mode" and "open_basedir" enabled.Documented ( http://de.php.net/manual/en/ref.session.php#ini.session.save-path ):  Values of "session.save_path" should or may be  **without**  ending slash.  For instance:<?php  // Valid only  *before* PHP 4.4.0:  ini_set( "session.save_path", "/var/httpd/kunde/phptmp" );?> will mean:  The directory "/var/httpd/kunde/phptmp/" will be used to write data and therefore must be writable by the web server.Starting with PHP 4.4.0 the server complains that "/var/httpd/kunde/" is not writable.Solution: Add an ending slash in call of ini_set (or probably whereever you set "session.save_path"), e.g.:<?php  // Note the slash on ".....phptmp/":  ini_set( "session.save_path", "/var/httpd/kunde/phptmp/" );?>Hope, that does help someone. 
dougal at gunters dot org
3 years ago
 It appears that if you use both the 'include_path' directives and 'open_basedir', that file searches will hit the include path *first*, before local files. But if 'open_basedir' is not in use, then local files are found first. For example, suppose you have code in '/var/www/myfile.php' which does:<?php  require_once('config.php');?>Further, assume that there is a local file '/var/www/config.php', and there is also a file '/var/local/php/config.php'.Next, if your php.ini has:  include_path = /var/local/php/Normally, this would look for '/var/www/config.php' first, and if not found, then it would try '/var/local/php/config.php'.But if you also have this in php.ini:  open_basedir = /var/www/:/var/local/php/Then the require would reverse the order of the search, and load '/var/local/php/config.php', even when the local 'config.php' file exists.Furthermore, if include_path contains directories not in open_basedir, you can end up with a fatal error. For example, change the directive to:  open_basedir = /var/www/:/var/local/includes/php/Now the require will first find '/var/local/php/config.php' from the include_path, try to include it, but be unable to because of the open_basedir restrictions. 
rlammers at linuxmail dot org
8 years ago
 This is a possible solution for a problem which seems to be a php-ini-problem but is not.If a $_POST is used with large fields e.g. textarea's with more than 120kb characters php returns a blank screen, even if the max_post_size is 8M.This problem may be caused by an apache-module SecFilter.Adding the following lines to the .htaccess solves the problem.SecFilterEngine OffSecFilterScanPOST OffI know this is not a php-issue, but i'm still posting it here since it looks like it is a php-problem and I did not find any sites or forums offering this solution.  txyoji at yahoo dot com 5 years ago  If you enable "open_basedir" option, it will disable the realpath_cache. This can be a significant performance hit.https://bugs.php.net/bug.php?id=53263  diamondeagle at webmail dot co dot za 8 days ago  Note regarding the upload_tmp_dir setting and UNC Paths:When using PHP on Windows OS and IIS FastCGI, if you need to use a UNC path to a folder on a network drive for the upload_tmp_dir setting then you must use three \ characters at the front of the UNC path. Windows and PHP use the first slash as an escape character, so if you only use two slashes then it passes a UNC path with just one backslash. That is not valid for UNC paths and you many experience problems when uploading files, such as errors saying that "PHP is missing a temporary folder".Correct:upload_tmp_dir = "\\\path\to\your\folder"Incorrect:upload_tmp_dir = "\\path\to\your\folder"  fernandobasso dot br at gmail dot com 2 years ago  This might help in case someone happens to maintain old applications with a charset other than utf-8.According to the docs, you can override the default charset if you use header().Suppose php.ini sets the default_charset to "UTF-8", but you need a legacy charset, like ISO-8859-1.Still,<?php header('Content-Type: text/html; Charset=ISO-8859-1'); ?>would not override the charset, just add it as well and the resultwas a response header like (note the two charsets): Content-Type:"text/html; Charset=ISO-8859-1;charset=UTF-8"I found it strange the default one as charset with a lowercase cas opposed to my custom charset with an uppercase C.What solved was to _override_ the charset using all lowercase lettersas well for the word “charset”:<?php header('content-type: text/html; charset=ISO-8859-1'); ?>Then, the double charset from the response headers disappeared, and only the single, custom charset remained.  AntonioK 8 years ago  Note that there is no way to disable eval() work by using disable_functions directive, because eval() is a language construct and not a function.Many people advise to disable such potentially-insecure functions like system(), exec(), passthru(), eval() and so on in php.ini when not running in safe mode, but eval() would still work even it listed in disable_functions.  -2 mrok at mrok dot com 10 years ago  Note that on some Unix systems (i.e. PHP 5.1.6 on Centos 5.2) include_path in php.ini should NOT be quoted.For example, instead of include_path='.:/usr/share/php'use include_path=.:/usr/share/phpUsing quotes does not cause any error message, but all of your require_once() directives will fail (indicating that file could not be opened) - unless full path to target file is provided.  -2 leo at korfu dot cz 13 years ago  "If the size of post data is greater than post_max_size..."It seems that a more elegant way is comparison between post_max_size and$_SERVER['CONTENT_LENGTH']. Please note that the latter includes not only size of uploaded file plus post data but also multipart sequences. Leo 
-3
amolitor at molitor-design dot com
9 years ago
 Amusingly, the include_path logically includes the current directory of the running file as the last entry all the time anyways, so part of the business about shoving "." into the include_path is spurious -- it's "there" on the end all the time, at least in the 5.2.12 source (see main/fopen_wrappers.c around line 503).This one had me goin' for a while. 
-1
7 months ago
 add enctype="multipart/form-data" to your <form> tag or it will not upload any file even if file_uploads=onex:<form method="POST" action="upload. php" enctype="multipart/form-data">// form contents</form> 
-5
iko at vision dot sk
7 years ago
 auto_globals_jit setting is also affecting \$_REQUEST superglobal in 5.3 It is not explicitly stated in documentation. 
-5
2 years ago
 Remember that open_basedir restriction does not affect exec functions. As long as you do not disable exec functions (see disable_functions, users will be able to use exec("/bin/cat [...]") to access sensitive world readable files. 
-7
kghbln
7 years ago
 Adding multiple directories to open_basedir:open_basedir = "/var/www/htdocs/:/var/www/tmp/" adds both paths /var/www/htdocs/ and /var/www/tmp/. Do not forget the trailing slash, otherwise the last directory will be considered as a prefix (< 5.3.4).On Windows you use ; as the seperator. 
-11
abc500x500 at gmail dot com
1 year ago
 Please illuminate this:memory_limit=128mb meaning which?1-per script only then if in a moment 1000 user request php script maximum only 128mb of server ram use6 by script.2-per script + per user if in a moment 1000 user request a php script about 1000*128mb=128gb ram use by script.Thanks 
-16
michael dot buergi at gmx dot net
6 years ago
 the ini-setting "detect_unicode" is indeed "zend.detect_unicode" (according to the phpinfo of my 5.4.4)