You are viewing a plain text version of this content. The canonical link for it is here.

Posted to bugs@httpd.apache.org by bu...@apache.org on 2003/08/21 17:31:20 UTC

DO NOT REPLY [Bug 15346] - CONNECT command accepted, but mod proxy is not loaded.

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 fb@toxis.com  2003-08-21 15:31 -------
Yes, we all know mod_php4's behavior is evil.
But on requests like "CONNECT www.google.com:80 HTTP/1.0" Apache
shouldn't set r->uri to "/" and r->content_type to "httpd/unix-directory"
So mod_dir gets invoked. (And mod_dir shoudn't try to find a local file
according to the DirectoryIndex rule. That's when /index.php comes into play.)
Please correct me if I'm wrong.

Apache 1.3.28
Compiled-in modules:
  http_core.c
  mod_log_config.c
  mod_mime.c
  mod_dir.c
  mod_access.c

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org