>> It sounds like having apache serve dynamic .html pages and nginx >> serve images on the same port means turning apache into a proxy for >> nginx which I'm hoping isn't too difficult. Could this pose any >> problems for an ecommerce site? > >> Changing completely from a user-facing apache to a user-facing nginx >> sounds fraught with peril. > > Yet this is the way it's done. If you have apache serve as a proxy for > nginx, you gain absolutely *nothing*; every inbound connection still > takes Apache resources, and that's exactly what you need to introduce a > proxy to alleviate.
Understood. Can anyone who has made a switch like this comment on potential (SSL-related?) pitfalls? - Grant
