Currently I'm using Jboss behind Apache HTTP Server. I wanted to know if there are any security/performance concerns that I may need to face if I remove Apache HTTPd.
I also wanted to remove the Firewall and looking for any configuration and implementation under Jboss to make it more secure.
Are there any know issues and also any known workaround for those.
But deploying your application with JBoss serving the Web requests directly may not be the optimal solution. First because the Tomcat web server embedded within JBoss is not the best server to serve static files and second because configuring Tomcat and JBoss for best performance and security is in general a complex and tedious task., – user7044 Feb 3 at 11:02you should not put your JBoss application as a Web front-end. Instead, you should use an Apache server and configure it to redirect specific Web application requests to your J2EE server. There are many many advantages in doing this:1. The Apache server can serve static files (CSS, images, javascript files) faster than JBoss/Tomcat. When you need it, you can activate SSL on Apache without having to change your application. 2. The Apache SSL implementation is faster compared to the Tomcat implementation (and a lot easier to configure!).` – user7044 Feb 4 at 17:01You can have a better control of HTTP headers. No need to develop any servlet filter for that. You can get compression out of the box. No need to develop another servlet filter either (no need to configure Tomcat connector either!)... I wanted to know if these are the benefits of using apache as front end. Are there any configuration that I need to make it on tomcat or jboss to perform as good as apache. – user7044 Feb 4 at 17:13