Migrating back to Apache 1.3 is always a fallback solution. My main intent in mentioning this workaround was to get some feedback on what it may have inadvertantly broken, since commenting out the line of code seems to make Apache 2 work very well with PHP on my machine with no observable, negative side effects (yet).

So, even though the apache2filter code is part of the PHP distribution, is it maintained by the Apache folks? Since the code in question (sapi_apache2.c) is part of the PHP distribution, I figured this (PHP-DEV) would be the correct forum, at least to start.

Thanks for everyone's responses so far!
Michael


At 10:19 AM 1/20/2003 -0500, you wrote:
Seems to me like there's not much that can be done on the php side but
more on the apache side.
In the meantime I'd suggest migrating your server to Apache 1.3.27 until
the problem is fixed since this may take quite a while.


On Mon, 2003-01-20 at 09:28, Michael D. Petersen wrote:
> The problem is described in a little more detail here:
> http://bugs.php.net/bug.php?id=17868

--
Xavier Spriet <[EMAIL PROTECTED]>


--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, visit: http://www.php.net/unsub.php

--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to