I can't speak for supercache, other people use it here with nginx, but
WHY would you proxy to Apache for PHP? :)

Take Apache out of the mix, you're wasting resources. Use PHP-FPM,
spawn-fcgi, or php -b. Why have an entire webserver daemon and its
overhead around just to parse PHP files.

As far as supercache rewrites/configuration/etc. in nginx, there's
been previous threads. All I know is I am usually able to do whatever
I need in nginx with minimal configuration. This thing is a monster.

On Sat, Dec 5, 2009 at 8:46 PM, nerdgrind <nginx-forum@nginx.us> wrote:
> I setup Nginx as the frontend server, and Apache as the backend to serve only PHP for Wordpress, however, after checking the headers I found Apache is sending cache-control, and other headers that should only be handled from the Nginx configuration. This leads me to believe that Apache may be serving the static as well as PHP files, when it should only be serving the PHP files.

_______________________________________________
nginx mailing list
nginx@nginx.org
http://nginx.org/mailman/listinfo/nginx