www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bnicho...@apache.org
Subject Re: mod_proxy/8175: mod_proxy does'nt work
Date Tue, 21 Aug 2001 20:50:12 GMT
[In order for any reply to be added to the PR database, you need]
[to include <apbugs@Apache.Org> 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!     ]

Synopsis: mod_proxy does'nt work

State-Changed-From-To: open-closed
State-Changed-By: bnicholes
State-Changed-When: Tue Aug 21 13:50:12 PDT 2001
    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.

View raw message