>Number: 2074
>Category: mod_rewrite
>Synopsis: mod_rewrite doesn't pass Proxy Throughput on internal
>subrequests
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: apache
>State: open
>Class: sw-bug
>Submitter-Id: apache
>Arrival-Date: Fri Apr 17 15:40:01 PDT 1998
>Last-Modified:
>Originator: [EMAIL PROTECTED]
>Organization:
apache
>Release: 1.2.6 and 1.3b5
>Environment:
N/A
>Description:
mod_rewrite has the following comment and code:
/*
* Ignore this rule on subrequests if we are explicitly
* asked to do so or this is a proxy-throughput or a
* forced redirect rule.
*/
if (r->main != NULL &&
(p->flags & RULEFLAG_IGNOREONSUBREQ ||
p->flags & RULEFLAG_PROXY ||
p->flags & RULEFLAG_FORCEREDIRECT ))
continue;
I don't understand the reasoning behind ignoring Proxy Throughput on
subrequests. Specifically, we wan't to be able to Proxy URI's from
server-parsed documents (mod_include) and this prevents that. Also,
this behavior is not consistent with ProxyPass, which is applied to
to internal sub-requests. One could work around this short-coming
like so:
ProxyPass /proxy/foobar.html http://domain.com/foobar.html
except that this is a lot more internal work for Apache (and it
also happens to break if your .html files are server-parsed, but
that's another PR I'm about to submit).
Finally, nothing is lost by removing this restriction. One could always
impose it on him/herself like so:
RewriteRule /foobar.html http://domain.com/foobar.html [P,NS]
>How-To-Repeat:
>Fix:
>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 leave the subject line UNCHANGED. This is not done]
[automatically because of the potential for mail loops. ]
