| Index du Forum » » Bugs, Probs ... |
Auteur |
[Résolu] - Bug dans nouvelle installation | PhilGuen
 986 
|  Posté : 23-05-2012 13:56
php.ini
; IMPORTANT
; ${path} is used to specify EasyPHP insta llation path
[PHP]
;;;;;;;;;;;;;;;;;;;
; About php.ini ;
;;;;;;;;;;;;;;;;;;;
; PHP's initialization file, generally called p hp.ini, is responsible for
; configuring many of the aspects of PHP's behavior.
; PHP attempts to find and load this configuration from a number of locations.
; The following is a summary of its s earch order:
; 1. SAPI module specific location.
; 2. The PHPRC environment variable. (As o f PHP 5.2.0)
; 3. A number of predefined registry keys& nbsp;on Windows (As of PHP 5.2.0)
; 4. Current working directory (except CLI)
; 5. The web server's directory (for SAPI& nbsp;modules), or directory of PHP
; (otherwise in Windows)
; 6. The directory from the --with-config-file- path compile time option, or the
; Windows directory (C:\windows or C:\winnt)
; See the PHP docs for more specific information.
; http://php.net/configuration.file
; The syntax of the file is extremely ;simple. Whitespace and Lines
; beginning with a semicolon are silently ignored (as you probably guessed).
; Section headers (e.g. [Foo]) are also si lently ignored, even though
; they might mean something in the future.
; Directives following the section heading [PAT H=/www/mysite] only
; apply to PHP files in the /www/mysite&nb sp;directory. Directives
; following the section heading [HOST=www.example.co m] only apply to
; PHP files served from www.example.com. Directives set in these
; special sections cannot be overridden by ;user-defined INI files or
; at runtime. Currently, [PATH=] and [HOST=]&nb sp;sections only work under
; CGI/FastCGI.
; http://php.net/ini.sections
; Directives are specified using the following& nbsp;syntax:
; directive = value
; Directive names are *case sensitive* - f oo=bar is different from FOO=bar.
; Directives are variables used to configure&nb sp;PHP or PHP extensions.
; There is no name validation. If PH P can't find an expected
; directive because it is not set or is mistyped, a default value will be used.
< br />
; The value can be a string, a number , a PHP constant (e.g. E_ALL or M_PI), one
; of the INI constants (On, Off, True,&nbs p;False, Yes, No and None) or an expression
; (e.g. E_ALL & ~E_NOTICE), a quoted s tring ("bar"), or a reference to a
; previously set variable or directive (e.g.&nb sp;${foo})
; Expressions in the INI file are limited& nbsp;to bitwise operators and parentheses:
; | bitwise OR
; ^ bitwise XOR
; & bitwise AND
; ~ bitwise NOT
; ! boolean NOT
; Boolean flags can be turned on using&nbs p;the values 1, On, True or Yes.
; They can be turned off using the va lues 0, Off, False or No.
; An empty string can be denoted by s imply not writing anything after the equal
; sign, or by using the None keyword:
; foo = ; sets foo to an empty string
; foo = None ; sets foo to an empty string
; foo = "None" ; sets foo to&n bsp;the string 'None'
; If you use constants in your value, ;and these constants belong to a
; dynamically loaded extension (either a PHP&nb sp;extension or a Zend extension),
; you may only use these constants *after* the line that loads the extension.
;;;;;;;;;;;;;;;;;;;
; About this file ;
;;;;;;;;;;;;;;;;;;;
; PHP comes packaged with two INI files.&n bsp;One that is recommended to be used
; in production environments and one that is recommended to be used in
; development environments.
; php.ini-production contains settings which hold&nb sp;security, performance and
; best practices at its core. But please&n bsp;be aware, these settings may break
; compatibility with older or less security&nbs p;conscience applications. We
; recommending using the production ini in ;production and testing environments.
; php.ini-development is very similar to its&nb sp;production variant, except it's
; much more verbose when it comes to errors. We recommending using the
; development version only in development envir onments as errors shown to
; application users can inadvertently leak othe rwise secure information.
;;;;;;;;;;;;;;;;;;;
; Quick Reference ;
;;;;;;;;;;;;;;;;;;;
; The following are all the settings which are different in either the production
; or development versions of the INIs with respect to PHP's default behavior.
; Please see the actual settings later in& nbsp;the document for more details as to why
; we recommend these changes in PHP's beha vior.
; allow_call_time_pass_reference
; Default Value: On
; Development Value: Off
; Production Value: Off
; display_errors
; Default Value: On
; Development Value: On
; Production Value: Off
; display_startup_errors
; Default Value: Off
; Development Value: On
; Production Value: Off
; error_reporting
; Default Value: E_ALL & ~E_NOTICE
< br />; Development Value: E_ALL | E_STRICT
; Production Value: E_ALL & ~E_DEPRE CATED
; html_errors
; Default Value: On
; Development Value: On
; Production value: Off
; log_errors
; Default Value: Off
; Development Value: On
; Production Value: On
; magic_quotes_gpc
; Default Value: On
; Development Value: Off
; Production Value: Off
; max_input_time
; Default Value: -1 (Unlimited)
; Development Value: 60 (60 seconds)
; Production Value: 60 (60 seconds)
; output_buffering
; Default Value: Off
; Development Value: 4096
; Production Value: 4096
; register_argc_argv
; Default Value: On
; Development Value: Off
; Production Value: Off
; register_long_arrays
; Default Value: On
; Development Value: Off
; Production Value: Off
; request_order
; Default Value: None
; Development Value: "GP"
; Production Value: "GP"
; session.bug_compat_42
; Default Value: On
; Development Value: On
; Production Value: Off
; session.bug_compat_warn
; Default Value: On
; Development Value: On
; Production Value: Off
; session.gc_divisor
; Default Value: 100
; Development Value: 1000
; Production Value: 1000
; session.hash_bits_per_character
; Default Value: 4
; Development Value: 5
; Production Value: 5
; short_open_tag
; Default Value: On
; Development Value: Off
; Production Value: Off
; track_errors
; Default Value: Off
; Development Value: On
; Production Value: Off
; url_rewriter.tags
; Default Value: "a=href,area=href,frame=src,form= ,fieldset="
; Development Value: "a=href,area=href,frame=src,i nput=src,form=fakeentry"
; Production Value: "a=href,area=href,frame=src,in put=src,form=fakeentry"
; variables_order
; Default Value: "EGPCS"
; Development Value: "GPCS"
; Production Value: "GPCS"
;;;;;;;;;;;;;;;;;;;;
; php.ini Options ;
;;;;;;;;;;;;;;;;;;;;
; Name for user-defined php.ini (.htaccess) fil es. Default is ".user.ini"
;user_ini.filename = ".user.ini"
; To disable this feature set this option& nbsp;to empty value
;user_ini.filename =
; TTL for user-defined php.ini files (time-to-l ive) in seconds. Default is 300 seconds (5&n bsp;minutes)
;user_ini.cache_ttl = 300
;;;;;;;;;;;;;;;;;;;;
; Language Options ;
;;;;;;;;;;;;;;;;;;;;
; Enable the PHP scripting language engine ;under Apache.
; http://php.net/engine
engine = On
; This directive determines whether or not ;PHP will recognize code between
; <? and ?> tags as PHP source which sh ould be processed as such. It's been
; recommended for several years that you n ot use the short tag "short cut" and
; instead to use the full <?php and ?> tag combination. With the wide&n bsp;spread use
; of XML and use of these tags by&nbs p;other languages, the server can become easily
< br />; confused and end up parsing the wrong&nb sp;code in the wrong context. But because
; this short cut has been a feature f or such a long time, it's currently still
; supported for backwards compatibility, but we recommend you don't use them.
; Default Value: On
; Development Value: Off
; Production Value: Off
; http://php.net/short-open-tag
short_open_tag = On
; Allow ASP-style <% %> tags.
; http://php.net/asp-tags
asp_tags = Off
; The number of significant digits displayed&nb sp;in floating point numbers.
; http://php.net/precision
precision = 14
; Enforce year 2000 compliance (will cause ;problems with non-compliant browsers)
; http://php.net/y2k-compliance
y2k_compliance = On
; Output buffering is a mechanism for cont rolling how much output data
; (excluding headers and cookies) PHP should&nb sp;keep internally before pushing that
; data to the client. If your application' s output exceeds this setting, PHP
; will send that data in chunks of ro ughly the size you specify.
; Turning on this setting and managing its maximum buffer size can yield some
; interesting side-effects depending on your ap plication and web server.
; You may be able to send headers and cookies after you've already sent output
; through print or echo. You also may ;see performance benefits if your server is
; emitting less packets due to buffered ou tput versus PHP streaming the output
; as it gets it. On production servers,&nb sp;4096 bytes is a good setting for performa nce
; reasons.
; Note: Output buffering can also be contr olled via Output Buffering Control
; functions.
; Possible Values:
; On = Enabled and buffer is u nlimited. (Use with caution)
; Off = Disabled
; Integer = Enables the buffer and& nbsp;sets its maximum size in bytes.
; Note: This directive is hardcoded to Off for the CLI SAPI
; Default Value: Off
; Development Value: 4096
; Production Value: 4096
; http://php.net/output-buffering
output_buffering = 4096
; You can redirect all of the output of your scripts to a function. For
; example, if you set output_handler to "m b_output_handler", character
; encoding will be transparently converted to&n bsp;the specified encoding.
; Setting any output handler automatically turn s on output buffering.
; Note: People who wrote portable scripts should not depend on this ini
; directive. Instead, explicitly set the output handler using ob_start().
; Using this ini directive may caus e problems unless you know what script
; is doing.
; Note: You cannot use both "mb_output_handler" with "ob_iconv_handler"
; and you cannot use both "ob_gzhan dler" and "zlib.output_compression".
; Note: output_handler must be empty if th is is set 'On' !!!!
; Instead you must use zlib.output_handl er.
; http://php.net/output-handler
;output_handler =
; Transparent output compression using the zlib library
; Valid values for this option are 'off',& nbsp;'on', or a specific buffer size
; to be used for compression (default is&n bsp;4KB)
; Note: Resulting chunk size may vary due& nbsp;to nature of compression. PHP
; outputs chunks that are few hundr eds bytes each as a result of
; compression. If you prefer a larg er chunk size for better
; performance, enable output_buffering in&nbs p;addition.
; Note: You need to use zlib.output_handler&nbs p;instead of the standard
; output_handler, or otherwise the outpu t will be corrupted.
; http://php.net/zlib.output-compression
zlib.output_compression = Off
; http://php.net/zlib.output-compression-level
;zlib.output_compression_level = -1
; You cannot specify additional output handlers if zlib.output_compression
; is activated here. This setting does the same as output_handler but in
; a different order.
; http://php.net/zlib.output-handler
;zlib.output_handler =
; Implicit flush tells PHP to tell the&nbs p;output layer to flush itself
; automatically after every output block. ;This is equivalent to calling the
; PHP function flush() after each and ever y call to print() or echo() and each
; and every HTML block. Turning this ;option on has serious performance
; implications and is generally recommended for debugging purposes only.
; http://php.net/implicit-flush
; Note: This directive is hardcoded to On& nbsp;for the CLI SAPI
implicit_flush = Off
; The unserialize callback function will be&nbs p;called (with the undefined class'
; name as parameter), if the unserializer finds an undefined class
; which should be instantiated. A warning appears if the specified function is
; not defined, or if the function doesn't& nbsp;!include!/implement the missing class.
; So only set this entry, if you real ly want to implement such a
; callback-function.
unserialize_callback_func =
; When floats & doubles are serialized ;store serialize_precision significant
; digits after the floating point. The def ault value ensures that when floats
; are decoded with unserialize, the data w ill remain the same.
serialize_precision = 17
; This directive allows you to enable and& nbsp;disable warnings which PHP will issue
; if you pass a value by reference at function call time. Passing values by
; reference at function call time is a&nbs p;deprecated feature which will be removed
; from PHP at some point in the near& nbsp;future. The acceptable method for passing a
; value by reference to a function is ;by declaring the reference in the functions
; definition, not at call time. This direc tive does not disable this feature, it
; only determines whether PHP will warn yo u about it or not. These warnings
; should enabled in development environments on ly.
; Default Value: On (Suppress warnings)
; Development Value: Off (Issue warnings)
; Production Value: Off (Issue warnings)
; http://php.net/allow-call-time-pass-reference
allow_call_time_pass_reference = Off
; Safe Mode
; http://php.net/safe-mode
safe_mode = Off
; By default, Safe Mode does a UID co mpare check when
; opening files. If you want to relax ;this to a GID compare,
; then turn on safe_mode_gid.
; http://php.net/safe-mode-gid
safe_mode_gid = Off
; When safe_mode is on, UID/GID checks are bypassed when
; including files from this directory and its subdirectories.
; (directory must also be in !include!_path&nbs p;or full path must
; be used when including)
; http://php.net/safe-mode-!include!-dir
safe_mode_!include!_dir =
; When safe_mode is on, only executables l ocated in the safe_mode_exec_dir
; will be allowed to be executed via the exec family of functions.
; http://php.net/safe-mode-exec-dir
safe_mode_exec_dir =
; Setting certain environment variables may be& nbsp;a potential security breach.
; This directive contains a comma-delimited lis t of prefixes. In Safe Mode,
; the user may only alter environment vari ables whose names begin with the
; prefixes supplied here. By default, use rs will only be able to set
; environment variables that begin with PHP_&nb sp;(e.g. PHP_FOO=BAR).
; Note: If this directive is empty, PHP will let the user modify ANY
; environment variable!
; http://php.net/safe-mode-allowed-env-vars
safe_mode_allowed_env_vars = PHP_
; This directive contains a comma-delimited lis t of environment variables that
; the end user won't be able to chang e using putenv(). These variables will be
< br />; protected even if safe_mode_allowed_env_vars is&nb sp;set to allow to change them.
; http://php.net/safe-mode-protected-env-vars
safe_mode_protected_env_vars = LD_LIBRARY_PATH
; open_basedir, if set, limits all file op erations to the defined directory
; and below. This directive makes most&nb sp;sense if used in a per-directory
; or per-virtualhost web server configuration f ile. This directive is
; *NOT* affected by whether Safe Mode is&n bsp;turned On or Off.
; http://php.net/open-basedir
;open_basedir =
; This directive allows you to disable cer tain functions for security reasons.
; It receives a comma-delimited list of fu nction names. This directive is
; *NOT* affected by whether Safe Mode is&n bsp;turned On or Off.
; http://php.net/disable-functions
disable_functions =
; This directive allows you to disable cer tain classes for security reasons.
; It receives a comma-delimited list of cl ass names. This directive is
; *NOT* affected by whether Safe Mode is&n bsp;turned On or Off.
; http://php.net/disable-classes
disable_classes =
; Colors for Syntax Highlighting mode. An ything that's acceptable in
; <span style="color: ???????"> would work.
; http://php.net/syntax-highlighting
;highlight.string = #DD0000
;highlight.comment = #FF9900
;highlight.keyword = #007700
;highlight.bg = #FFFFFF
;highlight.default = #0000BB
;highlight.html = #000000
; If enabled, the request will be allowed& nbsp;to complete even if the user aborts
; the request. Consider enabling it if exe cuting long requests, which may end up
; being interrupted by the user or a browser timing out. PHP's default behavior
; is to disable this feature.
; http://php.net/ignore-user-abort
;ignore_user_abort = On
; Determines the size of the realpath cach e to be used by PHP. This value should
; be increased on systems where PHP opens& nbsp;many files to reflect the quantity of
; the file operations performed.
; http://php.net/realpath-cache-size
;realpath_cache_size = 16k
; Duration of time, in seconds for which&n bsp;to cache realpath information for a given
; file or directory. For systems with rare ly changing files, consider increasing this
; value.
; http://php.net/realpath-cache-ttl
;realpath_cache_ttl = 120
;;;;;;;;;;;;;;;;;
; Miscellaneous ;
;;;;;;;;;;;;;;;;;
; Decides whether PHP may expose the fact& nbsp;that it is installed on the server
; (e.g. by adding its signature to the&nbs p;Web server header). It is no security
; threat in any way, but it makes it& nbsp;possible to determine whether you use PHP
; on your server or not.
; http://php.net/expose-php
expose_php = On
;;;;;;;;;;;;;;;;;;;
; Resource Limits ;
;;;;;;;;;;;;;;;;;;;
; Maximum execution time of each script, i n seconds
; http://php.net/max-execution-time
; Note: This directive is hardcoded to 0&n bsp;for the CLI SAPI
max_execution_time = 180
; Maximum amount of time each script may&n bsp;spend parsing request data. It's a good
; idea to limit this time on productions&n bsp;servers in order to eliminate unexpectedly
; long running scripts.
; Note: This directive is hardcoded to -1& nbsp;for the CLI SAPI
; Default Value: -1 (Unlimited)
; Development Value: 60 (60 seconds)
; Production Value: 60 (60 seconds)
; http://php.net/max-input-time
max_input_time = 60
; Maximum input variable nesting level
; http://php.net/max-input-nesting-level
;max_input_nesting_level = 64
; Maximum amount of memory a script may&nb sp;consume (128MB)
; http://php.net/memory-limit
memory_limit = 128M
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; Error handling and logging ;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; This directive informs PHP of which erro rs, warnings and notices you would like
; it to take action for. The recommended&n bsp;way of setting values for this
; directive is through the use of the ;error level constants and bitwise
; operators. The error level constants are ;below here for convenience as well as
; some common settings and their meanings.
; By default, PHP is set to take acti on on all errors, notices and warnings EXCEP T
; those related to E_NOTICE and E_STRICT, which together cover best practices and
; recommended coding standards in PHP. For ;performance reasons, this is the
; recommend error reporting setting. Your produ ction server shouldn't be wasting
; resources complaining about best practices an d coding standards. That's what
; development servers and development settings are for.
; Note: The php.ini-development file has this&n bsp;setting as E_ALL | E_STRICT. This
; means it pretty much reports everything which is exactly what you want during
; development and early testing.
;
; Error Level Constants:
; E_ALL ; - All errors and warnings (!include!s&nbs p;E_STRICT as of PHP 6.0.0)
; E_ERROR &nb sp;- fatal run-time errors
; E_RECOVERABLE_ERROR - almost fatal run-time& nbsp;errors
; E_WARNING - run-time warnings (non-fatal errors)
; E_PARSE &nb sp;- compile-time parse errors
; E_NOTICE -& nbsp;run-time notices (these are warnings which o ften result
; &nbs p; from a bug in& nbsp;your code, but it's possible that it wa s
; &nbs p; intentional (e.g., using an uninitialized variable and
; &nbs p; relying on the ;fact it's automatically initialized to an
; &nbs p; empty string)
; E_STRICT -& nbsp;run-time notices, enable to have PHP suggest changes
; &nbs p; to your code w hich will ensure the best interoperability
; &nbs p; and forward compati bility of your code
; E_CORE_ERROR - fatal erro rs that occur during PHP's initial startup
; E_CORE_WARNING - warnings (non-fatal& nbsp;errors) that occur during PHP's
; &nbs p; initial startup
; E_COMPILE_ERROR - fatal compile-time e rrors
; E_COMPILE_WARNING - compile-time warnings (non-fat al errors)
; E_USER_ERROR - user-generated& nbsp;error message
; E_USER_WARNING - user-generated warni ng message
; E_USER_NOTICE - user-generated notice message
; E_DEPRECATED - warn about code that will not work in future vers ions
; &nbs p; of PHP
; E_USER_DEPRECATED - user-generated deprecation war nings
;
; Common Values:
; E_ALL & ~E_NOTICE (Show all& nbsp;errors, except for notices and coding standa rds warnings.)
; E_ALL & ~E_NOTICE | E_STRICT (Show all errors, except for notices)
; E_COMPILE_ERROR|E_RECOVERABLE_ERROR|E_ERROR|E_CORE_ERROR&n bsp; (Show only errors)
; E_ALL | E_STRICT (Show all errors, warnings and notices including coding sta ndards.)
; Default Value: E_ALL & ~E_NOTICE
; Development Value: E_ALL | E_STRICT
; Production Value: E_ALL & ~E_DEPRECATED
; http://php.net/error-reporting
error_reporting = E_ALL | E_STRICT
; This directive controls whether or not a nd where PHP will output errors,
; notices and warnings too. Error output i s very useful during development, but
; it could be very dangerous in production environments. Depending on the code
; which is triggering the error, sensitive ;information could potentially leak
; out of your application such as database usernames and passwords or worse.
; It's recommended that errors be logged o n production servers rather than
; having the errors sent to STDOUT.
; Possible Values:
; Off = Do not display any err ors
; stderr = Display errors to STDERR (affects only CGI/CLI binaries!)
; On or stdout = Display errors&nbs p;to STDOUT
; Default Value: On
; Development Value: On
; Production Value: Off
; http://php.net/display-errors
display_errors = On
; The display of errors which occur during PHP's startup sequence are handled
; separately from display_errors. PHP's default ;behavior is to suppress those
; errors from clients. Turning the display ;of startup errors on can be useful in
; debugging configuration problems. But, it's s trongly recommended that you
; leave this setting off on production ser vers.
; Default Value: Off
; Development Value: On
; Production Value: Off
; http://php.net/display-startup-errors
display_startup_errors = On
; Besides displaying errors, PHP can also log errors to locations such as a
; server-specific log, STDERR, or a location&nb sp;specified by the error_log
; directive found below. While errors should&nb sp;not be displayed on productions
; servers they should still be monitored a nd logging is a great way to do that.
< br />; Default Value: Off
; Development Value: On
; Production Value: On
; http://php.net/log-errors
log_errors = On
; Set maximum length of log_errors. In err or_log information about the source is
; added. The default is 1024 and 0 al lows to not apply any maximum length at ;all.
; http://php.net/log-errors-max-len
log_errors_max_len = 1024
; Do not log repeated messages. Repeated e rrors must occur in same file on same
; line unless ignore_repeated_source is set tru e.
; http://php.net/ignore-repeated-errors
ignore_repeated_errors = Off
; Ignore source of message when ignoring r epeated messages. When this setting
; is On you will not log errors with& nbsp;repeated messages from different files or
; source lines.
; http://php.net/ignore-repeated-source
ignore_repeated_source = Off
; If this parameter is set to Off, th en memory leaks will not be shown (on
; stdout or in the log). This has onl y effect in a debug compile, and if
; error reporting !include!s E_WARNING in the&n bsp;allowed list
; http://php.net/report-memleaks
report_memleaks = On
; This setting is on by default.
;report_zend_debug = 0
; Store the last error/warning message in $php_errormsg (boolean). Setting this value
; to On can assist in debugging and i s appropriate for development servers. It should
; however be disabled on production servers.
; Default Value: Off
; Development Value: On
; Production Value: Off
; http://php.net/track-errors
track_errors = On
; Turn off normal error reporting and emit XML-RPC error XML
; http://php.net/xmlrpc-errors
;xmlrpc_errors = 0
; An XML-RPC faultCode
;xmlrpc_error_number = 0
; When PHP displays or logs an error, ;it has the capability of inserting html
; links to documentation related to that e rror. This directive controls whether
; those HTML links appear in error message s or not. For performance and security
; reasons, it's recommended you disable this&nb sp;on production servers.
; Note: This directive is hardcoded to Off for the CLI SAPI
; Default Value: On
; Development Value: On
; Production value: Off
; http://php.net/html-errors
html_errors = On
; If html_errors is set On PHP produces&nb sp;clickable error messages that direct
; to a page describing the error or f unction causing the error in detail.
; You can download a copy of the PHP manual from http://php.net/docs
; and change docref_root to the base URL&n bsp;of your local copy including the
; leading '/'. You must also specify the&n bsp;file extension being used including
; the dot. PHP's default behavior is to&nb sp;leave these settings empty.
; Note: Never use this feature for product ion boxes.
; http://php.net/docref-root
; Examples
;docref_root = "/phpmanual/"
; http://php.net/docref-ext
;docref_ext = .html
; String to output before an error message . PHP's default behavior is to leave
; this setting blank.
; http://php.net/error-prepend-string
; Example:
;error_prepend_string = "<span style='color: #ff0000'& gt;"
; String to output after an error message. PHP's default behavior is to leave
; this setting blank.
; http://php.net/error-append-string
; Example:
;error_append_string = "</span>"
; Log errors to specified file. PHP's defa ult behavior is to leave this value
; empty.
; http://php.net/error-log
; Example:
;error_log = php_errors.log
; Log errors to syslog (Event Log on NT, not valid in Windows 95).
;error_log = syslog
;;;;;;;;;;;;;;;;;
; Data Handling ;
;;;;;;;;;;;;;;;;;
; The separator used in PHP generated URLs to separate arguments.
; PHP's default setting is "&".
; http://php.net/arg-separator.output
; Example:
;arg_separator.output = "&"
; List of separator(s) used by PHP to ;parse input URLs into variables.
; PHP's default setting is "&".
; NOTE: Every character in this directive is considered as separator!
; http://php.net/arg-separator.input
; Example:
;arg_separator.input = ";&"
; This directive determines which super global& nbsp;arrays are registered when PHP
; starts up. If the register_globals directive& nbsp;is enabled, it also determines
; what order variables are populated into the global space. G,P,C,E & S are
; abbreviations for the following respective su per globals: GET, POST, COOKIE,
; ENV and SERVER. There is a performance&n bsp;penalty paid for the registration of
; these arrays and because ENV is not ;as commonly used as the others, ENV is
; is not recommended on productions servers.&nb sp;You can still get access to
; the environment variables through getenv() sh ould you need to.
; Default Value: "EGPCS"
; Development Value: "GPCS"
; Production Value: "GPCS";
; http://php.net/variables-order
variables_order = "GPCS"
; This directive determines which super global& nbsp;data (G,P,C,E & S) should
; be registered into the super global arra y REQUEST. If so, it also determines
; the order in which that data is reg istered. The values for this directive are
; specified in the same manner as the ;variables_order directive, EXCEPT one.
; Leaving this value empty will cause PHP& nbsp;to use the value set in the
; variables_order directive. It does not mean&n bsp;it will leave the super globals
; array REQUEST empty.
; Default Value: None
; Development Value: "GP"
; Production Value: "GP"
; http://php.net/request-order
request_order = "GP"
; Whether or not to register the EGPCS&nbs p;variables as global variables. You may
; want to turn this off if you don't& nbsp;want to clutter your scripts' global scope
< br />; with user data.
; You should do your best to write yo ur scripts so that they do not require
; register_globals to be on; Using form&n bsp;variables as globals can easily lead
; to possible security problems, if the co de is not very well thought of.
; http://php.net/register-globals
register_globals = Off
; Determines whether the deprecated long $HTTP_ *_VARS type predefined variables
; are registered by PHP or not. As th ey are deprecated, we obviously don't
; recommend you use them. They are on ;by default for compatibility reasons but
; they are not recommended on production s ervers.
; Default Value: On
; Development Value: Off
; Production Value: Off
; http://php.net/register-long-arrays
register_long_arrays = Off
; This directive determines whether PHP registe rs $argv & $argc each time it
; runs. $argv contains an array of all&nbs p;the arguments passed to PHP when a script
; is invoked. $argc contains an integer re presenting the number of arguments
; that were passed when the script was&nbs p;invoked. These arrays are extremely
; useful when running scripts from the com mand line. When this directive is
; enabled, registering these variables consumes ;CPU cycles and memory each time
; a script is executed. For performance re asons, this feature should be disabled
; on production servers.
; Note: This directive is hardcoded to On& nbsp;for the CLI SAPI
; Default Value: On
; Development Value: Off
; Production Value: Off
; http://php.net/register-argc-argv
register_argc_argv = Off
; When enabled, the SERVER and ENV variabl es 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&nbs p;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&n bsp;this directive to have any affect.
; http://php.net/auto-globals-jit
auto_globals_jit = On
; Maximum size of POST data that PHP will accept.
; http://php.net/post-max-size
post_max_size = 8M
; Magic quotes are a preprocessing feature ;of PHP where PHP will attempt to
; escape any character sequences in GET, P OST, COOKIE and ENV data which might
; otherwise corrupt data being placed in r esources such as databases before
; making that data available to you. Becau se of character encoding issues and
; non-standard SQL implementations across many databases, it's not currently
; possible for this feature to be 100%&nbs p;accurate. PHP's default behavior is to
; enable the feature. We strongly recommend&nbs p;you use the escaping mechanisms
; designed specifically for the database your&n bsp;using instead of relying on this
; feature. Also note, this feature has bee n deprecated as of PHP 5.3.0 and is
; scheduled for removal in PHP 6.
; Default Value: On
; Development Value: Off
; Production Value: Off
; http://php.net/magic-quotes-gpc
magic_quotes_gpc = on
; Magic quotes for runtime-generated data, e.g. data from SQL, from exec(), etc.
; http://php.net/magic-quotes-runtime
magic_quotes_runtime = on
; Use Sybase-style magic quotes (escape ' with '' instead of \').
; http://php.net/magic-quotes-sybase
magic_quotes_sybase = on
; Automatically add files before PHP document.
; http://php.net/auto-prepend-file
auto_prepend_file =
; Automatically add files after PHP document.
< br />; http://php.net/auto-append-file
auto_append_file =
; By default, PHP will output a character& nbsp;encoding using
; the !content-type:! header. To disable sending of the charset, simply
; set it to be empty.
;
; PHP's built-in default is text/html
; http://php.net/default-mimetype
default_mimetype = "text/html"
; PHP's default character set is set to&nb sp;empty.
; http://php.net/default-charset
;default_charset = "iso-8859-1"
; Always populate the $HTTP_RAW_POST_DATA variable.& nbsp;PHP's default behavior is
; to disable this feature.
; http://php.net/always-populate-raw-post-data
;always_populate_raw_post_data = On
;;;;;;;;;;;;;;;;;;;;;;;;;
; Paths and Directories ;
;;;;;;;;;;;;;;;;;;;;;;;;;
; UNIX: "/path1:/path2"
;!include!_path = ".:/php/!include!s"
;
; Windows: "\path1;\path2"
;!include!_path = ".;${path}\php\!include!s"
;
; PHP's default setting for !include!_path is&n bsp;".;/path/to/php/pear"
; http://php.net/!include!-path
; The root of the PHP pages, used onl y if nonempty.
; if PHP was not compiled with FORCE_REDIR ECT, you SHOULD set doc_root
; if you are running php as a CGI&nbs p;under any web server (other than IIS)
; see documentation for security issues. The alternate is to use the
; cgi.force_redirect configuration below
; http://php.net/doc-root
doc_root =
; The directory under which PHP opens the& nbsp;script using /~username used only
; if nonempty.
; http://php.net/user-dir
user_dir =
; Directory in which the loadable extensions&nb sp;(modules) reside.
; http://php.net/extension-dir
; extension_dir = "./"
; On windows:
extension_dir = "${path}\php\ext\"
; Whether or not to enable the dl() f unction. The dl() function does NOT work
; properly in multithreaded servers, such as&nb sp;IIS or Zeus, and is automatically
; disabled on them.
; http://php.net/enable-dl
enable_dl = Off
; cgi.force_redirect is necessary to provide se curity running PHP as a CGI under
; most web servers. Left undefined, PHP&n bsp;turns this on by default. You can
; turn it off here AT YOUR OWN RISK
< br />; **You CAN safely turn this off for IIS, in fact, you MUST.**
; http://php.net/cgi.force-redirect
;cgi.force_redirect = 1
; if cgi.nph is enabled it will force ;cgi to always sent Status: 200 with
; every request. PHP's default behavior is ;to disable this feature.
;cgi.nph = 1
; if cgi.force_redirect is turned on, and you are not running under Apache or Netscape
; (iPlanet) web servers, you MAY need to&n bsp;set an environment variable name that PHP
; will look for to know it is OK ;to continue execution. Setting this variable&nb sp;MAY
; cause security issues, KNOW WHAT YOU ARE DOING FIRST.
; http://php.net/cgi.redirect-status-env
;cgi.redirect_status_env = ;
; cgi.fix_pathinfo provides *real* PATH_INFO/PATH_TRANSLA TED 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. Sett ing
; this to 1 will cause PHP CGI to&nbs p;fix its paths to conform to the spec. ; A setting
; of zero causes PHP to behave as bef ore. Default is 1. You should fix&nbs p;your scripts
; to use SCRIPT_FILENAME rather than PATH_TRANS LATED.
; http://php.net/cgi.fix-pathinfo
;cgi.fix_pathinfo=1
; FastCGI under IIS (on WINNT based OS)&nb sp;supports the ability to impersonate
; security tokens of the calling client. & nbsp;This allows IIS to define the
; security context that the request runs u nder. mod_fastcgi under Apache
; does not currently support this feature (03/17/2002)
; Set to 1 if |
Cet article provient de NPDS
http://www.npds.org/viewtopic.php?topic=25512&forum=1
|
|
|