https://bz.apache.org/bugzilla/show_bug.cgi?id=61225
--- Comment #3 from Eric Covener <[email protected]> --- (In reply to Marc Stern from comment #2) > Correct me if I'm wrong, but httpd parses the first all global directives, > then the location ones. If we exit mod_proxy as soon as we see a matching > "!" (global or location, whatever), don't we have a generic solution ? I think by the time mod_proxy is checking at runtime, it has access to an array of global parsed ProxyPass directives, and a single per-location directive that is the result of the pair-wise merging (in this case over-riding) which is why the latter is referred to as the "quick" way in the code. My chief concern is preserving whatever weird semantics there were in 2.4.23 and earlier. I think that means per-location cannot be overridden by global directives. That's why part of fixing my own regression was just adding an envvar "no-proxy" that didn't have the baggage of 2.4.0-2.4.23 and worked a little more intuitively. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
