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