Try using all LocationMatch rather than mixing and matching and taking into account the order. On Fri, Oct 14, 2016 at 3:39 PM, Joe Muller <jmuller@xxxxxxxxxxx> wrote: > > > I am trying to migrate our Corporate Site from Sun One to Apache 2.4.18 > using the Weblogic 12.1.2 plug-in, targeting backend Weblogic 12c > applications. Essentially we have two applications on our website, and then > ‘everything else.’ The problem is getting the requests to go everything > else: > > > > This works: > > > > <Location /app1> > WLSRequest On > WebLogicHost xxxx > WebLogicPort yyyy > </Location> > > <Location /app2> > WLSRequest On > WebLogicHost xxxx > WebLogicPort yyyy > </Location> > > > > However if I add this entry, then Apache sends the requests for the above 2 > apps to this directive, which is what I don’t’ want: > > > > <LocationMatch /> > WLSRequest On > WebLogicHost xxxx > WebLogicPort yyyy > </LocationMatch> > > > > > > > <LocationMatch "^/(?!one|two)"> > WLSRequest On > WebLogicHost xxxx > WebLogicPort yyyy > </LocationMatch> -- Eric Covener covener@xxxxxxxxx --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|