-*- coding: utf-8 -*-
Changes with Apache 2.5.0
+ *) mod_proxy: Allow the per-request environment variable "no-proxy" to
+ be used as an alternative to ProxyPass /path !. This is primarily
+ to set exceptions for ProxyPass specified in <Location> context.
+ Use SetEnvIf, not SetEnv.
+
*) mod_http2: fix for crash when running out of memory.
[Robert Swiecki <robert@swiecki.net>, Stefan Eissing]
</Location>
</highlight>
+ <p> The "no-proxy" environment variable can be set to disable
+ <module>mod_proxy</module> processing the current request.
+ This variable should be set with <directive module="mod_setenvif"
+ >SetEnvIf</directive>, as <directive module="mod_env">SetEnv</directive>
+ is not evaluated early enough.</p>
+
</section> <!-- /envsettings -->
<section id="request-bodies"><title>Request Bodies</title>
specific location will take precedence.</p>
<p>For the same reasons, exclusions must come <em>before</em> the
- general <directive>ProxyPass</directive> directives.</p>
+ general <directive>ProxyPass</directive> directives. The "no-proxy"
+ environment variable is an alternative to exclusions, and is the only
+ way to configure an exclusion of a <directive>ProxyPass</directive>
+ directive in <directive module="core">Location</directive> context.
+ This variable should be set with <directive module="mod_setenvif"
+ >SetEnvIf</directive>, as <directive module="mod_env">SetEnv</directive>
+ is not evaluated early enough.
+ </p>
</note> <!-- /ordering_proxypass -->
|| !r->uri || r->uri[0] != '/') {
return DECLINED;
}
+
+ if (apr_table_get(r->subprocess_env, "no-proxy")) {
+ return DECLINED;
+ }
/* XXX: since r->uri has been manipulated already we're not really
* compliant with RFC1945 at this point. But this probably isn't