On Sat, May 2, 2009 at 9:55 PM, Ash Berlin <ash_c...@firemirror.com> wrote:
> > On 2 May 2009, at 10:31, Octavian Râşniţă wrote: > > Hi, >> >> In Catalyst::Manual::Cookbook I read >> >> # 502 is a Bad Gateway error, and will occur if the backend server is >> down >> # This allows us to display a friendly static page that says "down >> for >> # maintenance" >> Alias /_errors /var/www/MyApp/root/error-pages >> ErrorDocument 502 /_errors/502.html >> ... >> >> I've configured Apache this way, but if I stop the external Catalyst >> fastcgi app, instead of giving this HTTP error, it gives a 500 error, and in >> the logs I find: >> >> [Sat May 02 12:24:23 2009] [error] [client 89.122.248.135] (2)No such file >> or directory: FastCGI: failed to connect to server "/tmp/tb.fcgi": connect() >> failed >> [Sat May 02 12:24:23 2009] [error] [client 89.122.248.135] FastCGI: >> incomplete headers (0 bytes) received from server "/tmp/tb.fcgi" >> >> Do I need to do something more to make Apache give the 502 error? >> >> Thank you. >> >> Octavian >> > > Then the Cookbook is wrong. I've never seen anything but a 500 error from > any web server I've used. > > If you have a proxy in front, and the backend is down, you get a 502 error. -J
_______________________________________________ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
