On Thu, 2003-01-23 at 18:47, Brian Ashe wrote: > Actually, it is. It depends on what your index file type is.
I can produce that behavior if I make my server's default virtual host's index a php file, but not otherwise. That's sorta unexpected. Who defines this behavior? Is it an effect of mod_php that php files "support" CONNECT? > However, if you use (for example) PHP and have index.php as the default page, > it will accept the unusual method (if not prevented by "Limit" directives) > but wind up processing it as a "GET /" in the end. This is because, it will > be just like when a user doesn't put a trailing slash in the location bar, > Apache will automatically redirect it to /. I wouldn't go so far as to say that it's "just like" when a user forgets the trailing slash. When that happens, apache explicitly tells the browser to try again: $ telnet phantom.dragonsdawn.net 80 Trying 63.164.112.5... Connected to phantom.dragonsdawn.net. Escape character is '^]'. GET http://ispd.eburg.com/images HTTP/1.1 Host: ispd.eburg.com HTTP/1.1 301 Moved Permanently Date: Fri, 24 Jan 2003 03:45:26 GMT Server: Apache/1.3.27 (Unix) (Red-Hat/Linux) mod_ssl/2.8.12 OpenSSL/0.9.6b DAV/1.0.3 PHP/4.1.2 mod_perl/1.26 Location: http://ispd.eburg.com/images/ In fact, I don't see the parallel between the two behaviors at all... Either way, this seems a plausible explanation of the 200 response code to the CONNECT method. -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
