1: [PHP]
2:
3: ;;;;;;;;;;;;;;;;;;;
4: ; php.iniについて ;
5: ;;;;;;;;;;;;;;;;;;;
6: ; PHPの初期設定ファイルです。一般にphp.iniと呼ばれます。
7: ; PHPの多くの振る舞いを設定します。
8:
9: ; PHPは多くの場所からこの設定ファイルを探しロードします。
10: ; 以下は検索場所の概要です:
11: ; 1. SAPIモジュールがあるディレクトリ
12: ; 2. PHPRC環境変数に記載されたパス(PHP 5.2.0以降)
13: ; 3. Windows上での事前に定義済みのレジストリキー(PHP 5.2.0以降)
14: ; 4. 現在のワーキングディレクトリ (但し、CLIを除く)
15: ; 5. ウェブサーバーのディレクトリ(SAPIモジュール時)、またはPHPディレクトリ(Windows以外の場合)
16: ; 6. コンパイル時に--with-config-file-pathオプションで指定したディレクトリまたは、Windowsディレクトリ (C:\windowsまたは、C:\winnt)
17: ; より特殊な情報に関してはPHP docsを見てください。
18: ; http://php.net/configuration.file
19:
20: ; ファイルの構文は非常に単純です。セミコロンから始まる空白と行は静かに無視されます(たぶんあなたが推測したとおりに。)
21: ; また、節の見出し(例えば、[Foo])は静かに無視されます。彼らは、将来、何かを意味するかもしれませんが。
22:
23: ; セクション見出しである[PATH=/www/mysite]に続く指示は、/www/mysiteディレクトリのPHPファイルにのみ適用されます
24: ; セクション見出しである[HOST=www.example.com]に続く指示は、www.example.comで動作するPHPファイルにのみ適用されます
25: ; ユーザによって定義された初期ファイルやランタイムでは、これらの特別なセクションでの設定を上書きすることは出来ません。
26: ; 現在のところ、[PATH=]と[HOST=]セクションは、CGI/FastCGIの場合に動作します。
27: ; http://php.net/ini.sections
28:
29: ; 設定は、以下の構文を使用することで指定されます：
30: ; ディレクティブ = 値
31: ; ディレクティブ名は*大文字と小文字を区別します*
32: ; foo=baaとFOO=barは違う設定となります。
33: ; ディレクティブはPHPの設定やPHPの拡張を指定することに使用されます。
34: ; これらの名前は妥当性証が行われません。
35: ; もしもPHPが予想されたディレクティブを発見できなかった場合、デフォルト値を使用します。
36:
37: ; 値は文字列、数値、PHP定数(例：E_ALLまたはM_PI)、
38: ; INI定数のうちの一つ(On, Off, True, False, Yes, No 及び None)または、式(例：E_ALL & ~E_NOTICE)、
39: ; クォートされた文字列 ("bar")または、先に設定された変数や設定の参照（例：${foo}）
40: ; を使うことが出来ます。
41:
42: ; 初期ファイルの式は、ビット単位の演算子と括弧に制限されます:
43: ; | ビット単位 OR
44: ; ^ ビット単位 XOR
45: ; & ビット単位 AND
46: ; ~ ビット単位 NOT
47: ; ! 真偽値 NOT
48:
49: ; 真偽値フラグには1、On、TrueまたYesを使用することができます。
50: ; それらをひっくり返してオフにするには、0、Off、FalseまたはNoを使用することができます。
51:
52: ; イコールの後に何も書かないか、Noneキーワードを記述することで空文字を表現できます。
53: ; foo = ; fooに空文字をセットします
54: ; foo = None ; fooに空文字をセットします
55: ; foo = "None" ; fooに文字列'None'をセットします
56:
57: ; あなたが値に定数を使用し、その定数が動的にロードされたPHP拡張に属する場合(PHP拡張またはZend拡張)、
58: ; あなたは拡張がロードされた後にのみ、これらの定数を使用できます。
59:
60: ;;;;;;;;;;;;;;;;;;;;;;;;
61: ; このファイルについて ;
62: ;;;;;;;;;;;;;;;;;;;;;;;;
63: ; PHPには初期ファイルが二つパッケージされています。
64: ; 実稼働環境(production)での使用が勧められるものと、開発環境(development)で使用する事が勧められるものです。
65:
66: ; php.ini-production(実稼働環境用php.ini)は、その中核となるセキュリティ、パフォーマンス、ベストプラクティスを行う設定が含まれています。
67: ; しかし、注意が必要です。
68: ; これらの設定はより古いまたは、セキュリティの甘い性善説的アプリケーションとの互換性を壊すことがあります。
69: ; 私たちは実環境用設定を実運用環境とテスト環境での使用を推薦します。
70:
71: ; php.ini-development(開発環境用php.ini)は、エラー時に更に冗長になることを除いて実稼動環境用の設定ファイルと非常に似ています。
72: ; 私たちは開発環境でのみ開発環境用php.iniの使用を推奨します。
73: ; ユーザーがうっかりアプリケーションのエラーを表示した時に、それ以外のセキュアな情報を漏らすことが出来きるためです。
74:
75: ;;;;;;;;;;;;;;;;;;;;;;;;
76: ; クイックリファレンス ;
77: ;;;;;;;;;;;;;;;;;;;;;;;;
78:
79: ; これらは全てPHPのデフォルト、開発環境用php.ini、実稼働環境用php.iniで異なる設定です。
80: ; 私たちはこれらのPHPの設定を変更することを勧めます。
81: ; 理由などの詳細は後ほどドキュメントの実際の設定を参照してください。
82:
83: ; allow_call_time_pass_reference
84: ; Default Value: On
85: ; Development Value: Off
86: ; Production Value: Off
87:
88: ; display_errors
89: ; Default Value: On
90: ; Development Value: On
91: ; Production Value: Off
92:
93: ; display_startup_errors
94: ; Default Value: Off
95: ; Development Value: On
96: ; Production Value: Off
97:
98: ; error_reporting
99: ; Default Value: E_ALL & ~E_NOTICE
100: ; Development Value: E_ALL | E_STRICT
101: ; Production Value: E_ALL & ~E_DEPRECATED
102:
103: ; html_errors
104: ; Default Value: On
105: ; Development Value: On
106: ; Production value: Off
107:
108: ; log_errors
109: ; Default Value: Off
110: ; Development Value: On
111: ; Production Value: On
112:
113: ; magic_quotes_gpc
114: ; Default Value: On
115: ; Development Value: Off
116: ; Production Value: Off
117:
118: ; max_input_time
119: ; Default Value: -1 (Unlimited)
120: ; Development Value: 60 (60 seconds)
121: ; Production Value: 60 (60 seconds)
122:
123: ; output_buffering
124: ; Default Value: Off
125: ; Development Value: 4096
126: ; Production Value: 4096
127:
128: ; register_argc_argv
129: ; Default Value: On
130: ; Development Value: Off
131: ; Production Value: Off
132:
133: ; register_long_arrays
134: ; Default Value: On
135: ; Development Value: Off
136: ; Production Value: Off
137:
138: ; request_order
139: ; Default Value: None
140: ; Development Value: "GP"
141: ; Production Value: "GP"
142:
143: ; session.bug_compat_42
144: ; Default Value: On
145: ; Development Value: On
146: ; Production Value: Off
147:
148: ; session.bug_compat_warn
149: ; Default Value: On
150: ; Development Value: On
151: ; Production Value: Off
152:
153: ; session.gc_divisor
154: ; Default Value: 100
155: ; Development Value: 1000
156: ; Production Value: 1000
157:
158: ; session.hash_bits_per_character
159: ; Default Value: 4
160: ; Development Value: 5
161: ; Production Value: 5
162:
163: ; short_open_tag
164: ; Default Value: On
165: ; Development Value: Off
166: ; Production Value: Off
167:
168: ; track_errors
169: ; Default Value: Off
170: ; Development Value: On
171: ; Production Value: Off
172:
173: ; url_rewriter.tags
174: ; Default Value: "a=href,area=href,frame=src,form=,fieldset="
175: ; Development Value: "a=href,area=href,frame=src,input=src,form=fakeentry"
176: ; Production Value: "a=href,area=href,frame=src,input=src,form=fakeentry"
177:
178: ; variables_order
179: ; Default Value: "EGPCS"
180: ; Development Value: "GPCS"
181: ; Production Value: "GPCS"
182:
183: ;;;;;;;;;;;;;;;;;;;;
184: ; php.ini Options ;
185: ;;;;;;;;;;;;;;;;;;;;
186: ; ユーザ定義のphp.ini（.htaccess）ファイルの名前。デフォルトは".user.ini"です。
187: ;user_ini.filename = ".user.ini"
188:
189: ; この機能を無効にするにはこのオプションに空の値を設定する
190: ; To disable this feature set this option to empty value
191: ;user_ini.filename =
192:
193: ; ユーザ定義php.iniファイルの生存時間。デフォルトは300秒(5分)です。
194: ;user_ini.cache_ttl = 300
195:
196: ;;;;;;;;;;;;;;;;;;;;
197: ; 言語 Options ;
198: ;;;;;;;;;;;;;;;;;;;;
199:
200: ; このApacheでPHPスクリプト言語エンジンを有効にします。
201: ; http://php.net/engine
202: engine = On
203:
204: ; This directive determines whether or not PHP will recognize code between
205: ; <? and ?> tags as PHP source which should be processed as such. It's been
206: ; recommended for several years that you not use the short tag "short cut" and
207: ; instead to use the full <?php and ?> tag combination. With the wide spread use
208: ; of XML and use of these tags by other languages, the server can become easily
209: ; confused and end up parsing the wrong code in the wrong context. But because
210: ; this short cut has been a feature for such a long time, it's currently still
211: ; supported for backwards compatibility, but we recommend you don't use them.
212: ; Default Value: On
213: ; Development Value: Off
214: ; Production Value: Off
215: ; http://php.net/short-open-tag
216: short_open_tag = Off
217:
218: ; Allow ASP-style <% %> tags.
219: ; http://php.net/asp-tags
220: asp_tags = Off
221:
222: ; The number of significant digits displayed in floating point numbers.
223: ; http://php.net/precision
224: precision = 14
225:
226: ; Enforce year 2000 compliance (will cause problems with non-compliant browsers)
227: ; http://php.net/y2k-compliance
228: y2k_compliance = On
229:
230: ; Output buffering is a mechanism for controlling how much output data
231: ; (excluding headers and cookies) PHP should keep internally before pushing that
232: ; data to the client. If your application's output exceeds this setting, PHP
233: ; will send that data in chunks of roughly the size you specify.
234: ; Turning on this setting and managing its maximum buffer size can yield some
235: ; interesting side-effects depending on your application and web server.
236: ; You may be able to send headers and cookies after you've already sent output
237: ; through print or echo. You also may see performance benefits if your server is
238: ; emitting less packets due to buffered output versus PHP streaming the output
239: ; as it gets it. On production servers, 4096 bytes is a good setting for performance
240: ; reasons.
241: ; Note: Output buffering can also be controlled via Output Buffering Control
242: ; functions.
243: ; Possible Values:
244: ; On = Enabled and buffer is unlimited. (Use with caution)
245: ; Off = Disabled
246: ; Integer = Enables the buffer and sets its maximum size in bytes.
247: ; Note: This directive is hardcoded to Off for the CLI SAPI
248: ; Default Value: Off
249: ; Development Value: 4096
250: ; Production Value: 4096
251: ; http://php.net/output-buffering
252: output_buffering = 4096
253:
254: ; You can redirect all of the output of your scripts to a function. For
255: ; example, if you set output_handler to "mb_output_handler", character
256: ; encoding will be transparently converted to the specified encoding.
257: ; Setting any output handler automatically turns on output buffering.
258: ; Note: People who wrote portable scripts should not depend on this ini
259: ; directive. Instead, explicitly set the output handler using ob_start().
260: ; Using this ini directive may cause problems unless you know what script
261: ; is doing.
262: ; Note: You cannot use both "mb_output_handler" with "ob_iconv_handler"
263: ; and you cannot use both "ob_gzhandler" and "zlib.output_compression".
264: ; Note: output_handler must be empty if this is set 'On' !!!!
265: ; Instead you must use zlib.output_handler.
266: ; http://php.net/output-handler
267: ;output_handler =
268:
269: ; Transparent output compression using the zlib library
270: ; Valid values for this option are 'off', 'on', or a specific buffer size
271: ; to be used for compression (default is 4KB)
272: ; Note: Resulting chunk size may vary due to nature of compression. PHP
273: ; outputs chunks that are few hundreds bytes each as a result of
274: ; compression. If you prefer a larger chunk size for better
275: ; performance, enable output_buffering in addition.
276: ; Note: You need to use zlib.output_handler instead of the standard
277: ; output_handler, or otherwise the output will be corrupted.
278: ; http://php.net/zlib.output-compression
279: zlib.output_compression = Off
280:
281: ; http://php.net/zlib.output-compression-level
282: ;zlib.output_compression_level = -1
283:
284: ; You cannot specify additional output handlers if zlib.output_compression
285: ; is activated here. This setting does the same as output_handler but in
286: ; a different order.
287: ; http://php.net/zlib.output-handler
288: ;zlib.output_handler =
289:
290: ; Implicit flush tells PHP to tell the output layer to flush itself
291: ; automatically after every output block. This is equivalent to calling the
292: ; PHP function flush() after each and every call to print() or echo() and each
293: ; and every HTML block. Turning this option on has serious performance
294: ; implications and is generally recommended for debugging purposes only.
295: ; http://php.net/implicit-flush
296: ; Note: This directive is hardcoded to On for the CLI SAPI
297: implicit_flush = Off
298:
299: ; The unserialize callback function will be called (with the undefined class'
300: ; name as parameter), if the unserializer finds an undefined class
301: ; which should be instantiated. A warning appears if the specified function is
302: ; not defined, or if the function doesn't include/implement the missing class.
303: ; So only set this entry, if you really want to implement such a
304: ; callback-function.
305: unserialize_callback_func =
306:
307: ; When floats & doubles are serialized store serialize_precision significant
308: ; digits after the floating point. The default value ensures that when floats
309: ; are decoded with unserialize, the data will remain the same.
310: serialize_precision = 100
311:
312: ; This directive allows you to enable and disable warnings which PHP will issue
313: ; if you pass a value by reference at function call time. Passing values by
314: ; reference at function call time is a deprecated feature which will be removed
315: ; from PHP at some point in the near future. The acceptable method for passing a
316: ; value by reference to a function is by declaring the reference in the functions
317: ; definition, not at call time. This directive does not disable this feature, it
318: ; only determines whether PHP will warn you about it or not. These warnings
319: ; should enabled in development environments only.
320: ; Default Value: On (Suppress warnings)
321: ; Development Value: Off (Issue warnings)
322: ; Production Value: Off (Issue warnings)
323: ; http://php.net/allow-call-time-pass-reference
324: allow_call_time_pass_reference = Off
325:
326: ; Safe Mode
327: ; http://php.net/safe-mode
328: safe_mode = Off
329:
330: ; By default, Safe Mode does a UID compare check when
331: ; opening files. If you want to relax this to a GID compare,
332: ; then turn on safe_mode_gid.
333: ; http://php.net/safe-mode-gid
334: safe_mode_gid = Off
335:
336: ; When safe_mode is on, UID/GID checks are bypassed when
337: ; including files from this directory and its subdirectories.
338: ; (directory must also be in include_path or full path must
339: ; be used when including)
340: ; http://php.net/safe-mode-include-dir
341: safe_mode_include_dir =
342:
343: ; When safe_mode is on, only executables located in the safe_mode_exec_dir
344: ; will be allowed to be executed via the exec family of functions.
345: ; http://php.net/safe-mode-exec-dir
346: safe_mode_exec_dir =
347:
348: ; Setting certain environment variables may be a potential security breach.
349: ; This directive contains a comma-delimited list of prefixes. In Safe Mode,
350: ; the user may only alter environment variables whose names begin with the
351: ; prefixes supplied here. By default, users will only be able to set
352: ; environment variables that begin with PHP_ (e.g. PHP_FOO=BAR).
353: ; Note: If this directive is empty, PHP will let the user modify ANY
354: ; environment variable!
355: ; http://php.net/safe-mode-allowed-env-vars
356: safe_mode_allowed_env_vars = PHP_
357:
358: ; This directive contains a comma-delimited list of environment variables that
359: ; the end user won't be able to change using putenv(). These variables will be
360: ; protected even if safe_mode_allowed_env_vars is set to allow to change them.
361: ; http://php.net/safe-mode-protected-env-vars
362: safe_mode_protected_env_vars = LD_LIBRARY_PATH
363:
364: ; open_basedir, if set, limits all file operations to the defined directory
365: ; and below. This directive makes most sense if used in a per-directory
366: ; or per-virtualhost web server configuration file. This directive is
367: ; *NOT* affected by whether Safe Mode is turned On or Off.
368: ; http://php.net/open-basedir
369: ;open_basedir =
370:
371: ; This directive allows you to disable certain functions for security reasons.
372: ; It receives a comma-delimited list of function names. This directive is
373: ; *NOT* affected by whether Safe Mode is turned On or Off.
374: ; http://php.net/disable-functions
375: disable_functions =
376:
377: ; This directive allows you to disable certain classes for security reasons.
378: ; It receives a comma-delimited list of class names. This directive is
379: ; *NOT* affected by whether Safe Mode is turned On or Off.
380: ; http://php.net/disable-classes
381: disable_classes =
382:
383: ; Colors for Syntax Highlighting mode. Anything that's acceptable in
384: ; <span style="color: ???????"> would work.
385: ; http://php.net/syntax-highlighting
386: ;highlight.string = #DD0000
387: ;highlight.comment = #FF9900
388: ;highlight.keyword = #007700
389: ;highlight.bg = #FFFFFF
390: ;highlight.default = #0000BB
391: ;highlight.html = #000000
392:
393: ; If enabled, the request will be allowed to complete even if the user aborts
394: ; the request. Consider enabling it if executing long requests, which may end up
395: ; being interrupted by the user or a browser timing out. PHP's default behavior
396: ; is to disable this feature.
397: ; http://php.net/ignore-user-abort
398: ;ignore_user_abort = On
399:
400: ; Determines the size of the realpath cache to be used by PHP. This value should
401: ; be increased on systems where PHP opens many files to reflect the quantity of
402: ; the file operations performed.
403: ; http://php.net/realpath-cache-size
404: ;realpath_cache_size = 16k
405:
406: ; Duration of time, in seconds for which to cache realpath information for a given
407: ; file or directory. For systems with rarely changing files, consider increasing this
408: ; value.
409: ; http://php.net/realpath-cache-ttl
410: ;realpath_cache_ttl = 120
411:
412: ;;;;;;;;;;;;;;;;;
413: ; Miscellaneous ;
414: ;;;;;;;;;;;;;;;;;
415:
416: ; Decides whether PHP may expose the fact that it is installed on the server
417: ; (e.g. by adding its signature to the Web server header). It is no security
418: ; threat in any way, but it makes it possible to determine whether you use PHP
419: ; on your server or not.
420: ; http://php.net/expose-php
421: expose_php = On
422:
423: ;;;;;;;;;;;;;;;;;;;
424: ; Resource Limits ;
425: ;;;;;;;;;;;;;;;;;;;
426:
427: ; Maximum execution time of each script, in seconds
428: ; http://php.net/max-execution-time
429: ; Note: This directive is hardcoded to 0 for the CLI SAPI
430: max_execution_time = 30
431:
432: ; Maximum amount of time each script may spend parsing request data. It's a good
433: ; idea to limit this time on productions servers in order to eliminate unexpectedly
434: ; long running scripts.
435: ; Note: This directive is hardcoded to -1 for the CLI SAPI
436: ; Default Value: -1 (Unlimited)
437: ; Development Value: 60 (60 seconds)
438: ; Production Value: 60 (60 seconds)
439: ; http://php.net/max-input-time
440: max_input_time = 60
441:
442: ; Maximum input variable nesting level
443: ; http://php.net/max-input-nesting-level
444: ;max_input_nesting_level = 64
445:
446: ; Maximum amount of memory a script may consume (128MB)
447: ; http://php.net/memory-limit
448: memory_limit = 128M
449:
450: ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
451: ; Error handling and logging ;
452: ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
453:
454: ; This directive informs PHP of which errors, warnings and notices you would like
455: ; it to take action for. The recommended way of setting values for this
456: ; directive is through the use of the error level constants and bitwise
457: ; operators. The error level constants are below here for convenience as well as
458: ; some common settings and their meanings.
459: ; By default, PHP is set to take action on all errors, notices and warnings EXCEPT
460: ; those related to E_NOTICE and E_STRICT, which together cover best practices and
461: ; recommended coding standards in PHP. For performance reasons, this is the
462: ; recommend error reporting setting. Your production server shouldn't be wasting
463: ; resources complaining about best practices and coding standards. That's what
464: ; development servers and development settings are for.
465: ; Note: The php.ini-development file has this setting as E_ALL | E_STRICT. This
466: ; means it pretty much reports everything which is exactly what you want during
467: ; development and early testing.
468: ;
469: ; Error Level Constants:
470: ; E_ALL - All errors and warnings (includes E_STRICT as of PHP 6.0.0)
471: ; E_ERROR - fatal run-time errors
472: ; E_RECOVERABLE_ERROR - almost fatal run-time errors
473: ; E_WARNING - run-time warnings (non-fatal errors)
474: ; E_PARSE - compile-time parse errors
475: ; E_NOTICE - run-time notices (these are warnings which often result
476: ; from a bug in your code, but it's possible that it was
477: ; intentional (e.g., using an uninitialized variable and
478: ; relying on the fact it's automatically initialized to an
479: ; empty string)
480: ; E_STRICT - run-time notices, enable to have PHP suggest changes
481: ; to your code which will ensure the best interoperability
482: ; and forward compatibility of your code
483: ; E_CORE_ERROR - fatal errors that occur during PHP's initial startup
484: ; E_CORE_WARNING - warnings (non-fatal errors) that occur during PHP's
485: ; initial startup
486: ; E_COMPILE_ERROR - fatal compile-time errors
487: ; E_COMPILE_WARNING - compile-time warnings (non-fatal errors)
488: ; E_USER_ERROR - user-generated error message
489: ; E_USER_WARNING - user-generated warning message
490: ; E_USER_NOTICE - user-generated notice message
491: ; E_DEPRECATED - warn about code that will not work in future versions
492: ; of PHP
493: ; E_USER_DEPRECATED - user-generated deprecation warnings
494: ;
495: ; Common Values:
496: ; E_ALL & ~E_NOTICE (Show all errors, except for notices and coding standards warnings.)
497: ; E_ALL & ~E_NOTICE | E_STRICT (Show all errors, except for notices)
498: ; E_COMPILE_ERROR|E_RECOVERABLE_ERROR|E_ERROR|E_CORE_ERROR (Show only errors)
499: ; E_ALL | E_STRICT (Show all errors, warnings and notices including coding standards.)
500: ; Default Value: E_ALL & ~E_NOTICE
501: ; Development Value: E_ALL | E_STRICT
502: ; Production Value: E_ALL & ~E_DEPRECATED
503: ; http://php.net/error-reporting
504: ; error_reporting = E_ALL | E_STRICT
505:
506: ; This directive controls whether or not and where PHP will output errors,
507: ; notices and warnings too. Error output is very useful during development, but
508: ; it could be very dangerous in production environments. Depending on the code
509: ; which is triggering the error, sensitive information could potentially leak
510: ; out of your application such as database usernames and passwords or worse.
511: ; It's recommended that errors be logged on production servers rather than
512: ; having the errors sent to STDOUT.
513: ; Possible Values:
514: ; Off = Do not display any errors
515: ; stderr = Display errors to STDERR (affects only CGI/CLI binaries!)
516: ; On or stdout = Display errors to STDOUT
517: ; Default Value: On
518: ; Development Value: On
519: ; Production Value: Off
520: ; http://php.net/display-errors
521: display_errors = On
522:
523: ; The display of errors which occur during PHP's startup sequence are handled
524: ; separately from display_errors. PHP's default behavior is to suppress those
525: ; errors from clients. Turning the display of startup errors on can be useful in
526: ; debugging configuration problems. But, it's strongly recommended that you
527: ; leave this setting off on production servers.
528: ; Default Value: Off
529: ; Development Value: On
530: ; Production Value: Off
531: ; http://php.net/display-startup-errors
532: display_startup_errors = On
533:
534: ; Besides displaying errors, PHP can also log errors to locations such as a
535: ; server-specific log, STDERR, or a location specified by the error_log
536: ; directive found below. While errors should not be displayed on productions
537: ; servers they should still be monitored and logging is a great way to do that.
538: ; Default Value: Off
539: ; Development Value: On
540: ; Production Value: On
541: ; http://php.net/log-errors
542: log_errors = On
543:
544: ; Set maximum length of log_errors. In error_log information about the source is
545: ; added. The default is 1024 and 0 allows to not apply any maximum length at all.
546: ; http://php.net/log-errors-max-len
547: log_errors_max_len = 1024
548:
549: ; Do not log repeated messages. Repeated errors must occur in same file on same
550: ; line unless ignore_repeated_source is set true.
551: ; http://php.net/ignore-repeated-errors
552: ignore_repeated_errors = Off
553:
554: ; Ignore source of message when ignoring repeated messages. When this setting
555: ; is On you will not log errors with repeated messages from different files or
556: ; source lines.
557: ; http://php.net/ignore-repeated-source
558: ignore_repeated_source = Off
559:
560: ; If this parameter is set to Off, then memory leaks will not be shown (on
561: ; stdout or in the log). This has only effect in a debug compile, and if
562: ; error reporting includes E_WARNING in the allowed list
563: ; http://php.net/report-memleaks
564: report_memleaks = On
565:
566: ; This setting is on by default.
567: ;report_zend_debug = 0
568:
569: ; Store the last error/warning message in $php_errormsg (boolean). Setting this value
570: ; to On can assist in debugging and is appropriate for development servers. It should
571: ; however be disabled on production servers.
572: ; Default Value: Off
573: ; Development Value: On
574: ; Production Value: Off
575: ; http://php.net/track-errors
576: track_errors = On
577:
578: ; Turn off normal error reporting and emit XML-RPC error XML
579: ; http://php.net/xmlrpc-errors
580: ;xmlrpc_errors = 0
581:
582: ; An XML-RPC faultCode
583: ;xmlrpc_error_number = 0
584:
585: ; When PHP displays or logs an error, it has the capability of inserting html
586: ; links to documentation related to that error. This directive controls whether
587: ; those HTML links appear in error messages or not. For performance and security
588: ; reasons, it's recommended you disable this on production servers.
589: ; Note: This directive is hardcoded to Off for the CLI SAPI
590: ; Default Value: On
591: ; Development Value: On
592: ; Production value: Off
593: ; http://php.net/html-errors
594: html_errors = On
595:
596: ; If html_errors is set On PHP produces clickable error messages that direct
597: ; to a page describing the error or function causing the error in detail.
598: ; You can download a copy of the PHP manual from http://php.net/docs
599: ; and change docref_root to the base URL of your local copy including the
600: ; leading '/'. You must also specify the file extension being used including
601: ; the dot. PHP's default behavior is to leave these settings empty.
602: ; Note: Never use this feature for production boxes.
603: ; http://php.net/docref-root
604: ; Examples
605: ;docref_root = "/phpmanual/"
606:
607: ; http://php.net/docref-ext
608: ;docref_ext = .html
609:
610: ; String to output before an error message. PHP's default behavior is to leave
611: ; this setting blank.
612: ; http://php.net/error-prepend-string
613: ; Example:
614: ;error_prepend_string = "<font color=#ff0000>"
615:
616: ; String to output after an error message. PHP's default behavior is to leave
617: ; this setting blank.
618: ; http://php.net/error-append-string
619: ; Example:
620: ;error_append_string = "</font>"
621:
622: ; Log errors to specified file. PHP's default behavior is to leave this value
623: ; empty.
624: ; http://php.net/error-log
625: ; Example:
626: ;error_log = php_errors.log
627: ; Log errors to syslog (Event Log on NT, not valid in Windows 95).
628: ;error_log = syslog
629:
630: ;;;;;;;;;;;;;;;;;
631: ; Data Handling ;
632: ;;;;;;;;;;;;;;;;;
633:
634: ; Note - track_vars is ALWAYS enabled
635:
636: ; The separator used in PHP generated URLs to separate arguments.
637: ; PHP's default setting is "&".
638: ; http://php.net/arg-separator.output
639: ; Example:
640: ;arg_separator.output = "&"
641:
642: ; List of separator(s) used by PHP to parse input URLs into variables.
643: ; PHP's default setting is "&".
644: ; NOTE: Every character in this directive is considered as separator!
645: ; http://php.net/arg-separator.input
646: ; Example:
647: ;arg_separator.input = ";&"
648:
649: ; This directive determines which super global arrays are registered when PHP
650: ; starts up. If the register_globals directive is enabled, it also determines
651: ; what order variables are populated into the global space. G,P,C,E & S are
652: ; abbreviations for the following respective super globals: GET, POST, COOKIE,
653: ; ENV and SERVER. There is a performance penalty paid for the registration of
654: ; these arrays and because ENV is not as commonly used as the others, ENV is
655: ; is not recommended on productions servers. You can still get access to
656: ; the environment variables through getenv() should you need to.
657: ; Default Value: "EGPCS"
658: ; Development Value: "GPCS"
659: ; Production Value: "GPCS";
660: ; http://php.net/variables-order
661: variables_order = "GPCS"
662:
663: ; This directive determines which super global data (G,P,C,E & S) should
664: ; be registered into the super global array REQUEST. If so, it also determines
665: ; the order in which that data is registered. The values for this directive are
666: ; specified in the same manner as the variables_order directive, EXCEPT one.
667: ; Leaving this value empty will cause PHP to use the value set in the
668: ; variables_order directive. It does not mean it will leave the super globals
669: ; array REQUEST empty.
670: ; Default Value: None
671: ; Development Value: "GP"
672: ; Production Value: "GP"
673: ; http://php.net/request-order
674: request_order = "GP"
675:
676: ; Whether or not to register the EGPCS variables as global variables. You may
677: ; want to turn this off if you don't want to clutter your scripts' global scope
678: ; with user data. This makes most sense when coupled with track_vars - in which
679: ; case you can access all of the GPC variables through the $HTTP_*_VARS[],
680: ; variables.
681: ; You should do your best to write your scripts so that they do not require
682: ; register_globals to be on; Using form variables as globals can easily lead
683: ; to possible security problems, if the code is not very well thought of.
684: ; http://php.net/register-globals
685: register_globals = Off
686:
687: ; Determines whether the deprecated long $HTTP_*_VARS type predefined variables
688: ; are registered by PHP or not. As they are deprecated, we obviously don't
689: ; recommend you use them. They are on by default for compatibility reasons but
690: ; they are not recommended on production servers.
691: ; Default Value: On
692: ; Development Value: Off
693: ; Production Value: Off
694: ; http://php.net/register-long-arrays
695: register_long_arrays = Off
696:
697: ; This directive determines whether PHP registers $argv & $argc each time it
698: ; runs. $argv contains an array of all the arguments passed to PHP when a script
699: ; is invoked. $argc contains an integer representing the number of arguments
700: ; that were passed when the script was invoked. These arrays are extremely
701: ; useful when running scripts from the command line. When this directive is
702: ; enabled, registering these variables consumes CPU cycles and memory each time
703: ; a script is executed. For performance reasons, this feature should be disabled
704: ; on production servers.
705: ; Note: This directive is hardcoded to On for the CLI SAPI
706: ; Default Value: On
707: ; Development Value: Off
708: ; Production Value: Off
709: ; http://php.net/register-argc-argv
710: register_argc_argv = Off
711:
712: ; When enabled, the SERVER and ENV variables are created when they're first
713: ; used (Just In Time) instead of when the script starts. If these variables
714: ; are not used within a script, having this directive on will result in a
715: ; performance gain. The PHP directives register_globals, register_long_arrays,
716: ; and register_argc_argv must be disabled for this directive to have any affect.
717: ; http://php.net/auto-globals-jit
718: auto_globals_jit = On
719:
720: ; Maximum size of POST data that PHP will accept.
721: ; http://php.net/post-max-size
722: post_max_size = 8M
723:
724: ; Magic quotes are a preprocessing feature of PHP where PHP will attempt to
725: ; escape any character sequences in GET, POST, COOKIE and ENV data which might
726: ; otherwise corrupt data being placed in resources such as databases before
727: ; making that data available to you. Because of character encoding issues and
728: ; non-standard SQL implementations across many databases, it's not currently
729: ; possible for this feature to be 100% accurate. PHP's default behavior is to
730: ; enable the feature. We strongly recommend you use the escaping mechanisms
731: ; designed specifically for the database your using instead of relying on this
732: ; feature. Also note, this feature has been deprecated as of PHP 5.3.0 and is
733: ; scheduled for removal in PHP 6.
734: ; Default Value: On
735: ; Development Value: Off
736: ; Production Value: Off
737: ; http://php.net/magic-quotes-gpc
738: magic_quotes_gpc = Off
739:
740: ; Magic quotes for runtime-generated data, e.g. data from SQL, from exec(), etc.
741: ; http://php.net/magic-quotes-runtime
742: magic_quotes_runtime = Off
743:
744: ; Use Sybase-style magic quotes (escape ' with '' instead of \').
745: ; http://php.net/magic-quotes-sybase
746: magic_quotes_sybase = Off
747:
748: ; Automatically add files before PHP document.
749: ; http://php.net/auto-prepend-file
750: auto_prepend_file =
751:
752: ; Automatically add files after PHP document.
753: ; http://php.net/auto-append-file
754: auto_append_file =
755:
756: ; By default, PHP will output a character encoding using
757: ; the Content-type: header. To disable sending of the charset, simply
758: ; set it to be empty.
759: ;
760: ; PHP's built-in default is text/html
761: ; http://php.net/default-mimetype
762: default_mimetype = "text/html"
763:
764: ; PHP's default character set is set to empty.
765: ; http://php.net/default-charset
766: ;default_charset = "iso-8859-1"
767:
768: ; Always populate the $HTTP_RAW_POST_DATA variable. PHP's default behavior is
769: ; to disable this feature.
770: ; http://php.net/always-populate-raw-post-data
771: ;always_populate_raw_post_data = On
772:
773: ;;;;;;;;;;;;;;;;;;;;;;;;;
774: ; Paths and Directories ;
775: ;;;;;;;;;;;;;;;;;;;;;;;;;
776:
777: ; UNIX: "/path1:/path2"
778: ;include_path = ".:/php/includes"
779: ;
780: ; Windows: "\path1;\path2"
781: ;include_path = ".;c:\php\includes"
782: ;
783: ; PHP's default setting for include_path is ".;/path/to/php/pear"
784: ; http://php.net/include-path
785:
786: ; The root of the PHP pages, used only if nonempty.
787: ; if PHP was not compiled with FORCE_REDIRECT, you SHOULD set doc_root
788: ; if you are running php as a CGI under any web server (other than IIS)
789: ; see documentation for security issues. The alternate is to use the
790: ; cgi.force_redirect configuration below
791: ; http://php.net/doc-root
792: doc_root =
793:
794: ; The directory under which PHP opens the script using /~username used only
795: ; if nonempty.
796: ; http://php.net/user-dir
797: user_dir =
798:
799: ; Directory in which the loadable extensions (modules) reside.
800: ; http://php.net/extension-dir
801: ; extension_dir = "./"
802: ; On windows:
803: ; extension_dir = "ext"
804:
805: ; Whether or not to enable the dl() function. The dl() function does NOT work
806: ; properly in multithreaded servers, such as IIS or Zeus, and is automatically
807: ; disabled on them.
808: ; http://php.net/enable-dl
809: enable_dl = Off
810:
811: ; cgi.force_redirect is necessary to provide security running PHP as a CGI under
812: ; most web servers. Left undefined, PHP turns this on by default. You can
813: ; turn it off here AT YOUR OWN RISK
814: ; **You CAN safely turn this off for IIS, in fact, you MUST.**
815: ; http://php.net/cgi.force-redirect
816: ;cgi.force_redirect = 1
817:
818: ; if cgi.nph is enabled it will force cgi to always sent Status: 200 with
819: ; every request. PHP's default behavior is to disable this feature.
820: ;cgi.nph = 1
821:
822: ; if cgi.force_redirect is turned on, and you are not running under Apache or Netscape
823: ; (iPlanet) web servers, you MAY need to set an environment variable name that PHP
824: ; will look for to know it is O