https://issues.apache.org/bugzilla/show_bug.cgi?id=55412
Jeff Trawick <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Resolution|--- |INVALID --- Comment #3 from Jeff Trawick <[email protected]> --- Given that you're using mod_fastcgi, which isn't supported at the ASF, and these are user support-type questions anyway (http://httpd.apache.org/lists.html#http-users): >Can we implement fallback mechanism in Apache from Fcgi to cgi based on >certain condition. Say, if there is any issue in FCGI, it has to fall back to >CGI.? Ask the mod_fastcgi folks if it can fail gracefully in a way that allows another module to take control. (I seriously doubt it.) This would likely mean determining that the request processing had not proceeded far enough to change application state and changing the handler to something else and declining. The desired behavior is probably to get it to try harder to recover instead of backing down to CGI. (For example, if PHP can't run as a FastCGI server for whatever reason it is likely that it can't run as CGI either.) >Also i would like to know whether FCGI process can be restarted independently >based on certain conditions? Ask the mod_fastcgi folks. (I guess you mean a FastCGI process managed by mod_fastcgi.) -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
