ID: 19324
Updated by: derick@php.net
Reported By: wiseguy@ms10.url.com.tw
Status: Feedback
Bug Type: Output Control
Operating System: Solaris8 x86
PHP Version: 4.2.3
New Comment:
Okay, looks like an old bug resurfaced. Can you do the following test,
and stick to it very precise:
1. stop apache
2. start apache in single process mode like:
/path/to/apache/httpd -X
3. Request a page from a vhost/directory where PHP is enabled
4. Do that again :)
5. Request a page from a vhost/directory where PHP is disabled
6. Request a page from a vhost/directory where PHP is enabled (but not
explicit with php_engine = on, just the 'default')
7. Request a page from a vhost/directory where PHP is enabled (implicit
wirth php_engine = on)
Please tell us when you see the source and when not.
regards,
Derick
Previous Comments:
------------------------------------------------------------------------
[2002-09-28 09:55:58] wiseguy@ms10.url.com.tw
Yes, I do. But I use <Location> tag to include it.
because I want to make PHP can't work in some directories.
Why the showing source arise randomly ?
If I can't use "php_engine=off" , how I disable PHP
in some directories, please ?
------------------------------------------------------------------------
[2002-09-28 04:55:42] jmoore@php.net
You dont have php_engine=off in any of your apache vhosts do you?
- James
------------------------------------------------------------------------
[2002-09-28 04:44:55] wiseguy@ms10.url.com.tw
I used php4-200209280000 . the running result is the same.
------------------------------------------------------------------------
[2002-09-27 06:43:22] iliaa@php.net
Try the latest snapshot not the stable, the 'stable' brach is likely
not to have the fix you need.
------------------------------------------------------------------------
[2002-09-27 01:06:52] wiseguy@ms10.url.com.tw
No error as php4-200209241800 when I compiled
php4-STABLE-200209261800 .
But the running result is the same. :(
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/19324
--
Edit this bug report at http://bugs.php.net/?id=19324&edit=1