upgrading from 1.3.19 to 2.05 breaks
"Ed Kenny" <[email protected]>
| Newsgroups | gmane.comp.web.fastcgi.devel |
|---|---|
| Message-ID | <000201c5373e$f860ca40$b720fea9@KENNY001> |
Hi there,
I'm hoping someone here can help me.
I'd like to move to Apache 2, but I can't figure out why this upgrade
is breaking my FCGI External Server.
I'm using fastcgi 2.4.2 on the WEB server with Apache 2.052, no
problems.
On the APP server which is working fine running 1.319 , & fastcgi 2.4.0,
it breaks when I go to Apache 2 and either fastcgi 2.4.0 or 2.4.2. In
the APP logs I get Version 60! error, and Method Not Implemented. On the
WEB side logs I see x01/x01, which I take to mean no headers sent.
What has changed?
Here is my fastcgi configuration running on the APP server:
Alias cgi-bin/ "/ops/web/cgi-bin/"
Alias /cgi-bin/ "/ops/web/cgi-bin/"
<Directory "/ops/web/cgi-bin/">
AllowOverride None
Options ExecCGI
SetHandler fastcgi-script
Order allow,deny
Allow from all
</Directory>
AppClass /ops/web/cgi-bin/app1.exe -port 55551 -flush
<Location /cgi-bin/app1.exe>
SetHandler fastcgi-script
</Location>
<SNIP>
<SNIP>
AddHandler fastcgi-script .exe
___________________________________
fastcgi-developers mailing list
http://fastcgi.com/fastcgi-developers/