ID: 19113
User updated by: php_new at jdc dot parodius dot com
Reported By: php_new at jdc dot parodius dot com
Status: Bogus
Bug Type: Apache related
-Operating System: FreeBSD
+Operating System: All
PHP Version: 3.x, 4.x, 5.x
New Comment:
As mentioned a couple years ago, this may have gotten fixed somewhere
along the lines in Apache (or possibly PHP).
I just built a test system using FreeBSD 6.0, Apache 2.0.55, and PHP
5.1.1 (as a module) and *cannot* get this bug to appear.
But hear me out on this one if you could. :-)
Reason I have a hard time believing it's an Apache bug: if it was an
issue with interpreted handlers (such as PHP and mod_perl -- see one of
the other users' comments), then I would also expect the exact same bug
to appear when using mod_include (for server-parsed HTML documents).
But this doesn't happen.
Reason I have a hard time believing it's a PHP bug: because the problem
seems to have disappeared (at least on my test setup). Also, because
one of the other users stated that he had the same problem with
mod_perl loaded (but not with mod_php).
So either this got fixed in a PHP update (possibly mod_perl is still
broken then!), or an Apache update (more than likely an Apache APR
update).
I'm not going to sift through 3 years of ChangeLogs for PHP and Apache
to try and track this down, especially since I don't keep up-to-date
with *every* ChangeLog entry.
I'm fine with this being kept in Bogus status, but if someone has ideas
as to how this got fixed (and more importantly, in where) then it'd be
great if they could chime in here. I'd feel better knowing where this
bug was (Apache vs. PHP), rather than just some PHP developer telling
me "not a PHP problem".
Finally, I'm changing the OS to "All" because this problem had been
confirmed to exist on Win32 as well, not just UNIX.
Previous Comments:
------------------------------------------------------------------------
[2005-12-14 10:21:48] [EMAIL PROTECTED]
Not PHP problem.
------------------------------------------------------------------------
[2005-12-14 01:28:36] [EMAIL PROTECTED]
Does this work for you too:
NOSUCHMETHOD / HTTP/1.0
?
------------------------------------------------------------------------
[2005-12-14 01:16:46] php_new at jdc dot parodius dot com
This bug still applies to PHP 5.x, apparently. A user of mine just
recently asked me why his Apache logs were showing HTTP 200 status
codes with requests like "CONNECT" when mod_proxy isn't loaded, and I
pointed him to this bug.
Could a developer please look at this? This bug is over 3 years old
(!). Changing Status to Open...
Thanks.
------------------------------------------------------------------------
[2003-12-03 16:24:59] uhlar at fantomas dot sk
I don't know the apache's interface to modules, But I think that either
php should tell apache by initialization that it can handle GET, HEAD,
and POST method, ot the php should
check whether it is able to process the method (CONNECT in this case) -
if it does have handler for it.
I think that php does not have handler for CONNECT by default, thus it
should either reject the request or pass it to apache for later
processing.
mod_perl probably has the same bug, but unless apache does have an
interface for modules to specify which methods are they able to use AND
ignores the methods, it is a bug od mod_php versus mod_perl...
------------------------------------------------------------------------
[2003-08-24 10:26:07] messi at toxis dot com
I added the following three lines to Apache's mod_dir. This is ugly but
works fine for me. Unless there's another way to prevent mod_php4 from
getting invoked I'll use this on my machines.
Dunno if this will work with mod_proxy but I guess so.
--- src/modules/standard/mod_dir.c
+++ src/modules/standard/mod_dir.c
@@ -118,4 +118,7 @@
static int handle_dir(request_rec *r)
{
+ if (r->method_number == M_CONNECT)
+ return HTTP_NOT_IMPLEMENTED;
+
dir_config_rec *d =
(dir_config_rec *) ap_get_module_config(r->per_dir_config,
Use it at your own risk and only with Apache 1.3(.28)!
------------------------------------------------------------------------
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/19113
--
Edit this bug report at http://bugs.php.net/?id=19113&edit=1
