This week's book giveaway is in the OO, Patterns, UML and Refactoring forum.
We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line!
See this thread for details.
The moose likes Tomcat and the fly likes Preventing Apache bridge failure error page Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

JavaRanch » Java Forums » Products » Tomcat
Bookmark "Preventing Apache bridge failure error page" Watch "Preventing Apache bridge failure error page" New topic

Preventing Apache bridge failure error page

Rebeccah Quevedo-Prastein

Joined: Mar 17, 2011
Posts: 16

We are putting tomcat behind apache httpd server for security reasons, and only mapping in apache httpd those URIs that we want to expose to the general public.

Ideally, any other URIs in the context-path that are not mapped, we'd like to return a 404 error page, but right now, users are getting a "Failure of server APACHE bridge" error page. I don't just want to forward everything in the context, although I suppose I could. Would that be the simplest? Forward everything, and any pages that aren't on tomcat will get 404 generated by tomcat; and any unauthorized pages will get authorization failures... or is there a way to specify in apache httpd that unmapped pages should get a 404 error?

I think our INet group is using mod_jk to do the forwarding from apache httpd to tomcat.



P.S. Does Javaranch have a forum for apache httpd? If so, perhaps this should be posted there...
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link:
subject: Preventing Apache bridge failure error page
It's not a secret anymore!