https://bz.apache.org/bugzilla/show_bug.cgi?id=61225
--- Comment #5 from [email protected] --- (In reply to Marc Stern from comment #0) > Example 1 (from the doc): > <Location "/mirror/foo/"> > ProxyPass "http://backend.example.com/"; > </Location> > <Location "/mirror/foo/i"> > ProxyPass "!" > </Location> > GET /mirror/foo/i => not proxied: OK > > Example 1 (from the doc): > ProxyPass "/mirror/foo/i" "!" > ProxyPass "/mirror/foo" "http://backend.example.com"; > GET /mirror/foo/i => not proxied: OK > > Example 3: > ProxyPass "/mirror/foo/i" "!" > <Location "/mirror/foo/"> > ProxyPass "http://backend.example.com/"; > </Location> > GET /mirror/foo/i => proxied: not OK > > In example 3, we expect mod_proxy to stop processing anything, right? > In case we don't have to proxy a location, I think we should completely exit > mod_proxy. > Btw, this would also support the following case, which doesn't work for the > moment: > <Location "/mirror/foo/i"> > ProxyPass "!" > </Location> > <Location "/mirror/foo/"> > ProxyPass "http://backend.example.com/"; > </Location> Location is defined more global path first, most specific path second. ProxyPass is defined more specific path first, most global path second. Location has priority for the same "paths" over Directory or paths referenced in virtualhost context. As I see it, Example 3 does not apply because whatever you defined in virtualhost context for that path or sub-path will be "overwritten" by location that applies to the same path. And about example 4, no, Location does not work that way, when you define two Locations, as in example 1, most global should be defined first, more specific should be defined second, just the opposite to when you define ProxyPass directives. -- 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]
