mod_fastcgi 2.4.0 not backward compatible with 2.2.3

Ed Kenny <edkenny@...> writes:
 
Update: I've been trying different things with my FastCGI ExternalServer
setup and I believe I've isolated the problem. So far it seems the root
problem has nothing to do with the Apache versions in use.
 I am using mod_fastcgi 2.4.2 on the web side which works with
mod_fastcgi 2.2.3 running on the App side. When I 
try to upgrade mod_fastcgi on the App side to 2.4.0 or 2.4.2 it breaks
with these exact errors:
 
(WEB SERVER ERROR LOG):  [Mon Apr 04 17:09:18 2005] [error] [client
10.1.1.1] FastCGI: comm with server
"/usr/local/apache2/cgi-bin/app1.exe" 
aborted: protocol error: invalid version: 60 != FCGI_VERSION(1) [Mon Apr
04 17:09:18 2005] [error] [client 10.1.1.1] FastCGI: incomplete headers
(0 bytes) received from server "/usr/local/apache2/cgi-bin/app1.exe" 
 
(WEB SERVER ACCESS LOG):  10.1.1.1 - - [04/Apr/2005:17:09:18 -0400] "GET
/cs_alogin.exe HTTP/1.1" 500 1109  
 
(APP SERVER ERROR LOG): [Mon Apr  4 17:14:07 2005] [error] [client
10.1.1.1] Invalid method in request \x01\x01
 
So it seems mod_fastcgi 2.4.0 is not backward compatible with 2.2.3.
utilizing the External Server.
 
That would be OK by itself, but I do not think mod_fastcgi 2.2.3 is
compatible with Apache 2. I'll be trying that next just to be sure. 
 
I have not been able to find any relevant information on how I should
accomplish this migration to the current mod-fastcgi release from 2.2.3.

Can anyone give me a clue as to what I need to change in my code to make
this migration work? Or what changed from 2.2.3 to 2.4.0 to make earlier
implementations unusable?
 
Thanks,
Ed

___________________________________
fastcgi-developers mailing list
http://fastcgi.com/fastcgi-developers/