| 1 |
On Fri, Mar 8, 2013 at 12:59 PM, Grant <emailgrant@×××××.com> wrote: |
| 2 |
>>>>>>> Changing completely from a user-facing apache to a user-facing nginx |
| 3 |
>>>>>>> sounds fraught with peril. |
| 4 |
>>>> |
| 5 |
>>>> The last time I set this up was for one of our e-commerce sites on Centos. |
| 6 |
>>>> |
| 7 |
>>>> It went like this: |
| 8 |
>>>> |
| 9 |
>>>> install nginx |
| 10 |
>>>> vi config file |
| 11 |
>>>> change obvious stuff |
| 12 |
>>>> tweak location of nginx and backend web server |
| 13 |
>>>> restart stuff |
| 14 |
>>>> stuff worked |
| 15 |
>>>> |
| 16 |
>>>> Even the SSL certs was mind-bogglingly easy. Copy it over to nginx. |
| 17 |
>>>> Sorted. Done. |
| 18 |
> |
| 19 |
> You guys were so right. What an excellent http server/proxy. I used |
| 20 |
> this very simple howto: |
| 21 |
> |
| 22 |
> http://kbeezie.com/apache-with-nginx/ |
| 23 |
> |
| 24 |
> I can probably dump a lot of apache config. I still need SSL on both |
| 25 |
> servers even though only nginx faces the user? |
| 26 |
> |
| 27 |
> For imap proxy, nginx requires an HTTP auth server and I can't figure |
| 28 |
> out what that refers to. I can stick with imapproxy there. |
| 29 |
> |
| 30 |
> - Grant |
| 31 |
> |
| 32 |
|
| 33 |
You don't need SSL at both. Only nginx is enough. |
| 34 |
But to ensure nginx performs well at SSL, follow this - http://matt.io/entry/ur |
| 35 |
|
| 36 |
-- |
| 37 |
Nilesh Govindrajan |
| 38 |
http://nileshgr.com |
Archives