Hi jhbjava,
To support SSL in our development, staging and production environments,
I configure Apache http web server to perform the SSL transport, then configure the
apache http web server again so that it acts as a reverse proxy for a given
application. For example, when I access an applicaion using this url:
https://www.companyname.com/myapp1
I have set up the apache configuration to redirect all that https traffic to a
different machine running jboss on whatever port, say:
http://internalmachine.companyname.com:8080/myapp1
In this way, you can split the SSL work away from the jboss application server. The
advantages is better performance, plus it should be easier to configure apache for SSL
as it's such a typical thing to do with lots of resources on the web to explain how to
do it. Plus most of the major certificate providers have tutorials on how to uses
their SSL certificates on Apache, again easing your workload and understanding.
Best of luck whichever approach you use,
Conor
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3844088#3844088
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3844088
-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
