>Number: 5352 >Category: mod_proxy >Synopsis: No way to Limit ProxyRemote to specific methods >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: open >Class: change-request >Submitter-Id: apache >Arrival-Date: Mon Nov 22 18:40:01 PST 1999 >Last-Modified: >Originator: [EMAIL PROTECTED] >Organization: apache >Release: 1.3.9 >Environment: N/A >Description: Given that there are some methods that mod_proxy does not handle, it might be nice to allow the webmaster to forward those requests to a different proxy on a method by method basis.
Something like: <LimitExcept GET> ProxyRemote ftp http://rwftp-proxy.company.com:8888/ </LimitExcept> But Limit and LimitExcept only apply to access controls. Need they? >How-To-Repeat: Try to handle ftp downloads on proxyA but have proxyA forward ftp uploads to proxyB >Fix: Well, probably an extra field in the proxy_remote struct, possibly a change to proxy_cmds[] to allow the command to be wrapped in Limit, almost certainly a check for the method in proxy_handler(). If I get time I may have to try to cook up a patch to do this. It should be done properly though, i.e. cater for NoProxy and others too. >Audit-Trail: >Unformatted: [In order for any reply to be added to the PR database, you need] [to include <[EMAIL PROTECTED]> 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! ]
