> Michael's proxy suggestion is excellent too - I use nginx for this a > lot. It's amazingly easy to set up, a complete breath of fresh air after > the gigantic do-all beast that is apache. Performance depends a lot on > what your sites actually do, if every page is dynamic with changing > content then a reverse proxy doesn't help much. Only you know what your > page content is like.
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. - Grant
