For a variety of reasons I recently needed a reverse proxy(#1) and went with Apache 2.2 w/Google's mod_spdy. What are the advantages, if any (above and beyond that nginx has a lot of cred right now), of using nginx? In a prior build-out nginx didn't even support HTTP/1.1 on the inside side of the reverse proxy, while Apache 2.2 does.
#1 - We use it as a "least effort" geodistributed CDN. GeoDNS directs worldwide users (a small number of very high value users) to their local reverse proxy that has local caching of cacheable resources. Those proxies speak to the normal HTTP back-end servers through an SSH tunnel).
Apache's event MPM is not really an event MPM. It's a slightly modified worker MPM. It puts all idle connections (keepalive state) and listeners in a single thread. Each active connection gets its own thread.
The event MPM also behaves the same as the worker MPM for SSL connections.
Not having to deal with Apache style rewrite rules alone is worth it. Had a scenario recently where I had to try to unwind about 50 of those rules (client site). Made my head hurt.
#1 - We use it as a "least effort" geodistributed CDN. GeoDNS directs worldwide users (a small number of very high value users) to their local reverse proxy that has local caching of cacheable resources. Those proxies speak to the normal HTTP back-end servers through an SSH tunnel).