• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Preventing Apache bridge failure error page

 
Greenhorn
Posts: 16
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

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.

Thanks,

Rebeccah


P.S. Does Javaranch have a forum for apache httpd? If so, perhaps this should be posted there...
 
Screaming fools! It's nothing more than a tiny ad:
a bit of art, as a gift, the permaculture playing cards
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic