Upstream setup with proxy and fastcgi?

[Francis Daly]

On Fri, Apr 22, 2011 at 05:02:56AM -0400, TECK wrote:

Hi there,

> Ok, some updates on the testing. Using the configuration listed below
> does allow me to display index.php, but not index.html:

In your setup, when you access http://publicip/file.php, you want the
request to go to nginx, and then have nginx talk to one of the fastcgi
servers to get the response.

You report that this is working.

When you access http://publicip/file.html, you want the request to go
to nginx, and then what?

Do you want this nginx to serve /var/www/html/file.html from its
filesystem?; or do you want this nginx to talk to one of the other backend
web servers to let one of them provide the file from their filesystem?;
or something else?

> 	location / {
> 		proxy_pass		http://backend;
> 	}
> 
> 	location ~ \.php$ {
> 		fastcgi_pass		fastcgi;
> 		include			fastcgi.conf;
> 	}

> I tried to use only one server as main entrance but the load is going
> very high, once I run siege on it.
> How would I enable support for regular html files in the above
> configuration?

If you want nginx to serve the file itself, get rid of the "proxy_pass"
line.

If you want a backend server to handle it, this should already be
working. You report that it isn't, so check the logs of nginx, and of
the backend servers, to see if you can see where it fails.

(If that isn't enough to solve this, the in the reply, please include
what you do see instead of the content of /var/www/html/file.html when
you make the request. The http status code is probably significant.)

Good luck with it,

	f
-- 
Francis Daly        francis at daoine.org