#20372 [Bgs]: php_flag 'engine' keyword is case-sensitive

From: Date: Tue, 12 Nov 2002 01:34:52 +0000
Subject: #20372 [Bgs]: php_flag 'engine' keyword is case-sensitive
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-24653@lists.php.net to get a copy of this message
ID: 20372 Updated by: sniper@php.net Reported By: sandhoff@csus.edu Status: Bogus Bug Type: PHP options/info functions Operating System: HP-UX 10.20 PHP Version: 4.2.3 New Comment: on/off are just exception of the rule.. Previous Comments: ------------------------------------------------------------------------ [2002-11-11 19:04:11] sandhoff@csus.edu [Sorry about the gibberish] I can better understand case-sinsitivity if the VALUE field was also sesnitive, but 'oN' works just as well as 'On'. If it is the intention that case really matters than I apologize as I do not mean to waste your time. It just seemed odd to me that this was case-sensitive (and I spent too much time trying to 'fix' a problem I brought upon myself when I capitalized it). Thank you (sincerely) for your time. ------------------------------------------------------------------------ [2002-11-11 19:00:27] sandhoff@csus.edu Not to argue, but if the VALUE field is case-insensitive (which it is; ' The value field (On/Off) is NOT case sensitive, so it would ------------------------------------------------------------------------ [2002-11-11 18:24:28] sniper@php.net Where is it said that these keyword aren't case-sensitive? Not a bug. ------------------------------------------------------------------------ [2002-11-11 17:00:15] sandhoff@csus.edu In the Apache (1.3.27) httpd.conf file, it appears that the 'php_flag engine' key phrase is case-sensitive. Specifically, with PHP by default turned off, in a <Directory> block using the phrase 'php_flag Engine on', PHP is NOT available. However, using 'php_flag engine on' DOES enable PHP. Note that the difference is the capitalized keyword 'engine'. httpd -t does NOT report a syntax error with the capitalized keyword. From its description, bug #19996 (since fixed) may be relevant to this issue. Thank you for your time and effort. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=20372&edit=1

« previous php.bugs (#24653) next »