DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15346>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15346 CONNECT command accepted, but mod proxy is not loaded. ------- Additional Comments From [EMAIL PROTECTED] 2003-04-10 18:05 ------- > This is getting thrown back and forth. PHP says it's not their bug. Apache > says it's not their bug. So whose bug is which? Please look here to see > what > I mean: http://bugs.php.net/bug.php?id=19113 If this happens only with mod_php or mod_perl loaded, it's a bug in mod_php and/or mod_perl. > Should a new bug be filed? Or should this bug be reopened? No ;-) > PHP is assuming that it's a bug in the DSO code. Probably not. DSO has nothing to do with handling requests. > I've searched through php.ini and found > nothing regarding CONNECT method. I've even looked through the configure > options and saw nothing for CONNECT methods. By any assumption, PHP should be > dependant on whether or not Apache can handle CONNECT methods. PHP is designed to handle all you want. Apache relies on the module capabilities. The content-handler (e.g. mod_php, mod_cgi or the core-default-handler) is responsible for handling some arbitrary method. > So is there > anyone out there who can truly figure out what the problem is? And is this > small, yet seemingly annoying, problem will ever be fixed? All said above. There is *nothing* we can do here. If non-httpd-distributed modules don't stand to the rules it's obviously not a bug in Apache. Sorry. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
