sundialsvc4,

...I have had no “categorical problems” with FastCGI, in Linux, AIX, or Windows settings. It has especially not been the case that FastCGI had any problems vis-a-vis Apache 1 vs. 2.

I guess you haven't done much with any of the above. Unlike you, I only answer threads that I have experience with and have some knowledge of the subject. Apache 1 was a wonderful product! It is and was a great web-server. Apache 2 is the kitchen sink of security, product authorization, analysis, etc. etc.

My answer to the original OP, was to inform him/her about my similar experience and maybe save him/her from going through months of trying to get FastCGI to work with Apache2! If the application is complex (I'm sure 'hello world' will work!), he/she may find a better alternative desirable.

There are many things I could do with Apache1 that I cannot do with Appache2. I have had to change many scripts that ran for years with Apache1, and most of the time my changes were to reduce or eliminate functionality.

Since my experience with FastCGI and Apache2, changes may have been made to improve the compatibility between the products, but my experience at the time was to try and debug two products. I choose to eliminated one of the problems, and just like FastCGI, I use a small cgi script to talk to an in-memory compiled Perl frame-work that responds to the requests.

All of this is my experience with the subject, which I wanted to help the OP with. Sorry that it doesn't agree with your experiences.

Regards...Ed