Brent,
We secured access to the author instance using HTTPS/SSL because we do
not want passwords to be send unencrypted. Apache is responsible for the
SSL handling.
Ralf
Brent McArthur schrieb:
Hi There,
What is everyone's opinion on whether or not you should an apache web server
sitting in front of tomcat magnolia in a production environment? Are there any
performance benefits?
I'm just curious.
A large proportion of my IT experience has been in developing custom java web
applications. As a default architecture, we pretty much always went with an
apache web server, tomcat app server approach so that apache web server could
effectively serve up all static content while leaving the dynamic stuff to
tomcat. This is also good from a scalability perspective.
But with Magnolia, a large proportion of what I would normally consider "static" is managed by the CMS through the DMS (images, style sheets, etc.). This means, Apache will really be doing nothing but passing all requests through to Tomcat (mod_jk).
So I put the question out there, what benefits does one get by using an apache
web server if magnolia is only hosting a single magnolia site?
I did a search on the wiki
http://wiki.magnolia-cms.com/dosearchsite.action?queryString=apache which tells
you how to configure apache but doesn't necessarily explain the benefits unless
you're hosting multiple sites with the one magnolia instance.
Cheers,
Brent
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
