lighttpd AND FastCGI server disconnect handling

Greetings all,

I have been experimenting on lighttpd and a fastcgi
RESPONDER perl app using FCGI.pm and
CGI::Fast(actually my clone) modules. The perl fastcgi
app listens to a specific tcp socket for incoming
requests from lighttpd. So far everything is working
well for me, except I discovered one thing:

When the perl fastcgi app DIES or exits *accidentally*
AFTER FCGI accept() BEFORE flushing out anything
(headers at least), lighttpd OUTPUTS:
   a. HTTP Status 200 OK
   b. a blank content body
   c. Connection: Close

Item [b] and [c] is understandable. But item no. [a]?

So my questions:
1) What is the correct behavior as per FastCGI spec?
2) I was kind of expecting lighttpd to send out a
Status 500 or the like, not 200, so can this behavior
at least be addressed? 
3) If so, where? lighttpd OR the perl fastcgi app?
4) I have been digging out the mailing lists of 
fastcgi, could this have something to do with SIGNALs?
(Though I'm thinking SIGNALS have to do with
webserver->fcgi.server communication, not the other
way around).

My need: To send out content+Status 200 OK explicitly
only when my fcgi app says so.

Hope I could learn something from developers with
similar experience. 

Thanks all!

Dexter Tad-y



__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
___________________________________
fastcgi-developers mailing list
http://fastcgi.com/fastcgi-developers/