Received: (qmail 21911 invoked by uid 501); 13 Aug 2001 18:18:08 -0000 Message-Id: <20010813181808.21910.qmail@apache.org> Date: 13 Aug 2001 18:18:08 -0000 From: Andreas "Türpe" Reply-To: andreas.tuerpe@lmkgmbh.de To: submit@bugz.apache.org Subject: mod_proxy does'nt work X-Send-Pr-Version: 3.110 >Number: 8175 >Category: mod_proxy >Synopsis: mod_proxy does'nt work >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: closed >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Mon Aug 13 11:20:00 PDT 2001 >Closed-Date: Tue Aug 21 13:50:12 PDT 2001 >Last-Modified: Tue Aug 21 13:50:12 PDT 2001 >Originator: andreas.tuerpe@lmkgmbh.de >Release: 1.3.20 >Organization: >Environment: Novell NetWare 5, Support Pack Revision 06 Apache for NetWare, Version 1.03, 21 May 2001, binary distribution from http://developer.novell.com/ndk/modapach.htm >Description: The Apache as WebServer works fine well. After enabling the proxy functionality, apache does'nt work as proxy. The error message in the logs is "Filename is not valid: proxy:/http://developer.novell.com/" The related configuration is: ServerName www.lmkgmbh.de # Alias vor proxy.lmkgmbh.de LoadModule proxy_module modules/proxy.nlm AddModule mod_proxy.c ProxyRequests on AllowCONNECT 80 8080 CacheRoot "CACHE:/ICACHE" # novell-volume:/cache-directory Options FollowSymLinks AllowOverride None Allow from .lmkgmbh.de # mydomain ProxyVia On CacheSize 1024000 CacheGcInterval 4 CacheMaxExpire 24 CacheLastModifiedFactor 0.1 CacheDefaultExpire 1 ProxyReceiveBufferSize 1024 ProxyDomain .lmkgmbh.de The same configuration (as Proxy) works under other circumstances like linux-system well. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: State-Changed-From-To: open-closed State-Changed-By: bnicholes State-Changed-When: Tue Aug 21 13:50:12 PDT 2001 State-Changed-Why: Fixed the problem with MOD_PROXY by changing how ap_os_canonical_filename() and ap_os_is_path_absolute() deal with paths and file names. ap_os_canonical_filename() was altering proxy:http://blah into proxy:/http:/blah which made it incompatible with MOD_PROXY. Therefore Apache would report back that it had an invalid filename. This function now recognizes special file names and does not try to canonicalize them. ap_os_is_path_absolute() also incorrectly recognized a special file name such as proxy:http://blah as being a NetWare volume and path. Given both of these fixes, mod_proxy now works correctly. It is recommended that ProxyReceiveBufferSize be left at the default unless you really know what you are doing. This directive appears to conflict with the normal operation of the sockets. >Unformatted: [In order for any reply to be added to the PR database, you need] [to include in the Cc line and make sure the] [subject line starts with the report component and number, with ] [or without any 'Re:' prefixes (such as "general/1098:" or ] ["Re: general/1098:"). If the subject doesn't match this ] [pattern, your message will be misfiled and ignored. The ] ["apbugs" address is not added to the Cc line of messages from ] [the database automatically because of the potential for mail ] [loops. If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request from a ] [developer. Reply only with text; DO NOT SEND ATTACHMENTS! ]