Apache tomcat error 40310/11/2023 ![]() ![]() In our case, Apache Tomcat Server is installed in /opt/tomcat/apache-tomcat-8.5.32 directory. To migrate this issue, you need to add the following code into your web.xml file located at /conf directory. Let’s look at a common 404 error message on a site running on Apache Tomcat Server.Ĭustomization of these error responses can be configured in the configuration file web.xml. A generic 404 page can frustrate these newbies and make them leave your site never to return. However, your site visitors might be new to the Internet or not fully understand how websites work. Whatever the reason, when the visitor hits that error page, you want it to be a funnel back into your site or you risk losing your visitor to your competition.Įspecially when we talk about Apache’s Tomcat Server, an error page always reveals your server’s sensitive information like Apache Version etc. As a web savvy person, you automatically understand why a 404 error was returned. Perhaps the visitor adds a strange extension to the end of the web address, or maybe she has bookmarked an old page and your organizational structure has changed. Logs show dev/test honoring this response (200 ok) while PROD tomcat throws a 403 forbidden, but only for a few SELECT URLs that happen to be authenticated callback URLs resulting from APEX database unpacked by ORDS responseĪny help with this issue would be greatly appreciated.A 404 error is an HTTP status code that means that the page you were trying to reach on a website couldn’t be found on their server.Īt some point, a visitor is going to stumble onto a 403/404/500 error page. The NetId shows up on the logs to indicate authentication working as configured. The location given is an authenticated URL under the Tomcat Shib listener and the logs indicated Apache-Shib had indeed filled in REMOTE_USER for this pass to Tomcat AJP. When the browser tried to honor the 302 redirect location given by ORDS-Tomcat, this resulted in Tomcat throwing a 403 Forbidden. The way this works is that ORDS on the Tomcat server receives a response from APEX database on port 1521, then unpacks the Pl/sql gateway response (a 302 from PL/sql gateway) then ORDS sends this response to the Browser as a HTTP response. TCPdump showed the last response from APEX Pl/sql gateway was a HTTP-302 redirect location, not a 403. ![]() Below is some analysis our Tomcat engineer has done: We have not been able to resolve this with Oracle support. Application ids are executed by URL suffix invoking an APEX application: (/f?p=103)Ĭhecked all privileges related to Apex and all seem to be matching dev, test. Only executing an APEX Application ids seems to throw a 403. Using Authenticated Okta Tomcat ORDS service to login into the Apex workspace and run SQL workshop works and running other Apex functionality Other Prod Apex applications work as before the upgrade if not using remote_header SAML type authentication. Suddenly application that currently works fine in dev, test and was working in Prod has started to throw 403 errors during authentication process.Įrror seems to be occurring during callback to application authentication process.Īpex version 5.1.3 same on dev, test, prodĭEV/TEST urls all work OK with the same patches applied to Tomcat. We recently applied Tomcat security patches in production that had already been applied in dev and test to linux ORDS servers.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |