#19808 [Bgs]: auto_prepend_file none and apache2

ID: 19808 User updated by: scribles@synthesis.net Reported By: scribles@synthesis.net Status: Bogus Bug Type: Apache2 related Operating System: linux PHP Version: 4.2.3 New Comment: If you read my original post you’ll notice I pointed out that I tried it without quotes and it still didn’t work. Also I’m using PHP 4.2.2 with Apache 1.3.26 and it works with or without the quotes. I am positive that the problem is the behavior of the software and not how I have it configured. Is this something that is being changed in 4.3.0 then? Sorry to be so persistent, but I would appreciate knowing if this is something that is going to fix itself in a future release or if I need to find a workaround for my problem. Thank you for the clarification. Previous Comments: ------------------------------------------------------------------------ [2002-10-08 13:27:13] iliaa@php.net Sorry, but your problem does not imply a bug in PHP itself. For a list of more appropriate places to ask for help using PHP, please visit http://www.php.net/support.php as this bug system is not the appropriate forum for asking support questions. Thank you for your interest in PHP. Sorry about that, you are quite right, none option is supported. However, you should not quote the word 'none'. You'll find that the none option will work properly if it is not quoted. ex. php_value auto_prepend_file none I've just verified this behaviour using PHP 4.3.0-dev and Apache 2. ------------------------------------------------------------------------ [2002-10-08 12:06:12] scribles@synthesis.net Thank you for dismissing my claim so quickly however you are wrong. The manual, which I did double check, supports what I’m saying… specifically http://www.php.net/manual/en/configuration.directives.php BEGIN QUOTE 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 include() function, so include_path is used. The special value none disables auto-prepending. END QUOTE Please note the last line, which notes the behavior that is broken in the version I am using. The reason for this behavior is the way Apache applies configuration directives to the directory structure. In the structure /foo/bar anything you apply to the directory foo is also applied to bar and any other subdirectories. If you configure foo to auto_prepend a file you must specifically configure bar to not auto_prepend if you do not want that same behavior in that directory. Hence the need for “auto_prepend none”. Not only is this behavior documented by the PHP manual and necessary to configure Apache it is also how every version of PHP I’ve used over the past several years has behaved. I’m not sure if the problem is with PHP or Apache however I can assure you the behavior I’m experiencing is a bug. ------------------------------------------------------------------------ [2002-10-08 08:11:28] iliaa@php.net Thank you for taking the time to write to us, but this is not a bug. Please double-check the documentation available at http://www.php.net/manual/ and the instructions on how to report a bug at http://bugs.php.net/how-to-report.php If you do not was to have a file automatically appended or prepended, simply do not specify a auto_prepend_file or auto_append_file entry. ------------------------------------------------------------------------ [2002-10-07 20:21:23] scribles@synthesis.net PHP 4.2.3 and Apache 2.0.43 on Linux When using php_value auto_prepend_file “none” in Apache configuration files or .htaccess files the script tries to prepend a file called “none” instead of not prepending a file like it should resulting in the following error. Same thing with auto_append_file. Warning: Failed opening 'none' for inclusion (include_path='.:/home/synthesis/www/include') in Unknown on line 0 I’ve tried it without quotes and upper case without any effect. Other PHP directives seem to work fine in configuration files and .htaccess files. I’m guessing Apache changed the meaning of “none”, but that’s just a guess and I have no idea if it’s intentional or accidental. I wasn’t sure if this belonged here or as an Apache bug. Sorry if I’m in the wrong place. -scribles ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=19808&edit=1