Hello, I would never recommend to use <Location /> , you should use <Location /app> instead for all the applications in the weblogic server, which are all probably deployed in a specific context rather than /. If for any reason one is too lazy to care or still want to exclude some content from being proxied to the weblogic the weblogic plugin includes the directive: WLExcludePathOrMimeType You should play with it. Cheers El jue, 21 oct 2021 a las 8:03, ohaya (<ohaya@xxxxxxxxx.invalid>) escribió: > > I haven't figured out how to get rid of the Forbidden problem, but I've found a kind of workaround to get the Apache to send a response... Since accessing the /foo was causing a Forbidden (403) error, I added an ErrorDocument: > > ===================================================== > ErrorDocument 403 "This is the response message that I want" > Alias "/foo" "/apps/products/apache/instances/apache_oam/foo" > > <Location /> > . > . > . > </Location> > ===================================================== > > That does cause the browser to get a response message, but I KNOW it is a real hack, and also NOT GOOD, because I think that with the ErrorDocument, that means every time a user gets a 403 error, they are going to see that "This is the response message that I want" response message :(!! > > So far to try to avoid the Forbidden error, I've tried adding: > > <Directory "/apps/products/apache/instances/apache_oam/foo"> > Require all granted > <.Directory> > > But I still get the Forbidden error. > > If anyone knows how I cat avoid the Forbidden error (so I wouldn't need the ErrorDocument), please help? > > Thanks, > Jim > > On Wednesday, October 20, 2021, 03:40:53 PM EDT, ohaya <ohaya@xxxxxxxxx> wrote: > > > Hi, > > We are using Apache 2.4.48. This Apache is primarily acting as a proxy, and we use the WebLogic Plugin for Apache to connect from the Apache to a WebLogic server/backend. > > In the Apache ssl.conf, we have a <VirtualHost>, and in that <VirtualHost>, they have a <Location />: > > <VirtualHost _default_:443 _default_:14101> > . > . > . > <Location /> > WLSRequest On > SetHandler weblogic-handler > WebLogicCluster xxx.foo.com:14101 > WLCookieName OAM_JSESSIONID > SecureProxy ON > WLSSLWallet ".../wallet" > Debug OFF > WLLogFile "/logs/oam_location.out" > </Location> > > . > . > . > <VirtualHost> > > Because of the <Location />, this Apache is not able to serve local content (e.g., html, etc.), but I have a requirement to be able to serve a single HTML page from this Apache. > > Unfortunately, they want to keep that <Location /> in the ssl.conf, so I am trying to figure out how I might be able to configure the Apache so that it can serve that HTML page that I am needing? > > I have tried to add an Alias in front of the <Location />, i.e.: > > =================================================== > Alias "/foo" "/apps/products/apache/instances/apache_oam/foo" > > <Location /> > . > . > . > </Location> > =================================================== > > But I am getting a Forbidden response. Also sometimes the browser seems to "loop", adding "/index.html" to the end of the URL in the address bar. > > So I was wondering: Is there a way to accomplish what I am trying to do, without disturbing the <Location />?? > > Thanks, > Jim > -- Daniel Ferradal HTTPD Project #httpd help at Libera.Chat --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|