[BACK]Return to php.ini-development CVS log [TXT] [DIR] Up to [ELWIX - Embedded LightWeight unIX -] / embedaddon / php

Diff for /embedaddon/php/php.ini-development between versions 1.1.1.4 and 1.1.1.5

version 1.1.1.4, 2013/10/14 08:02:08 version 1.1.1.5, 2014/06/15 20:03:41
Line 83 Line 83
 ; development version only in development environments as errors shown to  ; development version only in development environments as errors shown to
 ; application users can inadvertently leak otherwise secure information.  ; application users can inadvertently leak otherwise secure information.
   
   ; This is php.ini-development INI file.
   
 ;;;;;;;;;;;;;;;;;;;  ;;;;;;;;;;;;;;;;;;;
 ; Quick Reference ;  ; Quick Reference ;
 ;;;;;;;;;;;;;;;;;;;  ;;;;;;;;;;;;;;;;;;;
Line 136 Line 138
 ;   Development Value: "GP"  ;   Development Value: "GP"
 ;   Production 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  ; session.gc_divisor
 ;   Default Value: 100  ;   Default Value: 100
 ;   Development Value: 1000  ;   Development Value: 1000
Line 197 Line 189
 engine = On  engine = On
   
 ; This directive determines whether or not PHP will recognize code between  ; This directive determines whether or not PHP will recognize code between
; <? and ?> tags as PHP source which should be processed as such. It's been; <? and ?> tags as PHP source which should be processed as such. It is
; recommended for several years that you not use the short tag "short cut" and; generally recommended that <?php and ?> should be used and that this feature
; instead to use the full <?php and ?> tag combination. With the wide spread use; should be disabled, as enabling it may result in issues when generating XML
; of XML and use of these tags by other languages, the server can become easily; documents, however this remains supported for backward compatibility reasons.
; confused and end up parsing the wrong code in the wrong context. But because; Note that this directive does not control the <?= shorthand tag, which can be
; this short cut has been a feature for such a long time, it's currently still; used regardless of this directive.
; supported for backwards compatibility, but we recommend you don't use them. 
 ; Default Value: On  ; Default Value: On
 ; Development Value: Off  ; Development Value: Off
 ; Production Value: Off  ; Production Value: Off
Line 582  html_errors = On Line 573  html_errors = On
 ; http://php.net/error-log  ; http://php.net/error-log
 ; Example:  ; Example:
 ;error_log = php_errors.log  ;error_log = php_errors.log
; Log errors to syslog (Event Log on NT, not valid in Windows 95).; Log errors to syslog (Event Log on Windows).
 ;error_log = syslog  ;error_log = syslog
   
 ;windows.show_crt_warning  ;windows.show_crt_warning
Line 1019  mail.add_x_header = On Line 1010  mail.add_x_header = On
 ; The path to a log file that will log all mail() calls. Log entries include  ; The path to a log file that will log all mail() calls. Log entries include
 ; the full path of the script, line number, To address and headers.  ; the full path of the script, line number, To address and headers.
 ;mail.log =  ;mail.log =
; Log mail to syslog (Event Log on NT, not valid in Windows 95).; Log mail to syslog (Event Log on Windows).
 ;mail.log = syslog  ;mail.log = syslog
   
 [SQL]  [SQL]
Line 1474  session.gc_maxlifetime = 1440 Line 1465  session.gc_maxlifetime = 1440
 ;       For example, the following script would is the equivalent of  ;       For example, the following script would is the equivalent of
 ;       setting session.gc_maxlifetime to 1440 (1440 seconds = 24 minutes):  ;       setting session.gc_maxlifetime to 1440 (1440 seconds = 24 minutes):
 ;          find /path/to/sessions -cmin +24 -type f | xargs rm  ;          find /path/to/sessions -cmin +24 -type f | xargs rm
   
 ; PHP 4.2 and less have an undocumented feature/bug that allows you to  
 ; to initialize a session variable in the global scope.  
 ; PHP 4.3 and later will warn you, if this feature is used.  
 ; You can disable the feature and the warning separately. At this time,  
 ; the warning is only displayed, if bug_compat_42 is enabled. This feature  
 ; introduces some serious security problems if not handled correctly. It's  
 ; recommended that you do not use this feature on production servers. But you  
 ; should enable this on development servers and enable the warning as well. If you  
 ; do not enable the feature on development servers, you won't be warned when it's  
 ; used and debugging errors caused by this can be difficult to track down.  
 ; Default Value: On  
 ; Development Value: On  
 ; Production Value: Off  
 ; http://php.net/session.bug-compat-42  
 session.bug_compat_42 = On  
   
 ; This setting controls whether or not you are warned by PHP when initializing a  
 ; session value into the global space. session.bug_compat_42 must be enabled before  
 ; these warnings can be issued by PHP. See the directive above for more information.  
 ; Default Value: On  
 ; Development Value: On  
 ; Production Value: Off  
 ; http://php.net/session.bug-compat-warn  
 session.bug_compat_warn = On  
   
 ; Check HTTP Referer to invalidate externally stored URLs containing ids.  ; Check HTTP Referer to invalidate externally stored URLs containing ids.
 ; HTTP_REFERER has to contain this substring for the session to be  ; HTTP_REFERER has to contain this substring for the session to be
Removed from v.1.1.1.4  
changed lines
  Added in v.1.1.1.5

FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>