Project

General

Profile

Actions
Copy link

Bug #37

closed

avoid 500 client errors when multiple fcgi servers defined for URI

Added by glen about 20 years ago. Updated about 18 years ago.

Status:
Fixed
Priority:
Normal
Category:
core
Target version:
-
ASK QUESTIONS IN Forums:

Description

if i have multiple fcgi servers defined for URI, and lighttpd just in the client request notices that fcgi server is unavailable, it will serve out client error 500.

improvement request would be that the next fcgi server is tried first, and response from that next fcgi server is returned to the client (of course cycling to the next available fcgi server if that one failed too)

Actions
Copy link
 #1

Updated by jan about 20 years ago

  • Status changed from New to Fixed
  • Resolution set to fixed

This is implemented since 1.3.8 IIRC. With the latest fixes it should be stable and working.

The only case were it is expected to fail with a 500 is if you get this:

(mod_fastcgi.c.1907) unexpected end-of-file (perhaps the fastcgi process died): pid: 16584 fcgi-fd: 26 remote-fd: 9
(mod_fastcgi.c.2778) response not sent, request sent: 567 connection-fd: 9 fcgi-fd: 26

which means that the request has been forwarded to the fastcgi-proc successfully, but the fastcgi-proc died afterwards. lighttpd can't tell if it is safe to forward this request to another fastcgi proc or not. (session handling, calcutations, ...)

Informing the client is the only safe option here.

Actions
Copy link

Also available in: Atom