[Catalyst] Bad gateway error

[J. Shirley]

On Sat, May 2, 2009 at 9:55 PM, Ash Berlin <ash_cpan at firemirror.com> wrote:

>
> On 2 May 2009, at 10:31, Octavian R=E2=BAni=FE=E3 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, an=
d in
>> the logs I find:
>>
>> [Sat May 02 12:24:23 2009] [error] [client 89.122.248.135] (2)No such fi=
le
>> or directory: FastCGI: failed to connect to server "/tmp/tb.fcgi": conne=
ct()
>> 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.scsys.co.uk/pipermail/catalyst/attachments/20090503/a0aa2=
3e8/attachment.htm