Since CGI working here and Michael Purdy is a big CGI user, he hasn't
reported anything, it has to be the script engine itself.

There were major enhancements in the CGI web processor in 451.5 and let
see if there were and changes in 451.6.... This was the only fix in
451.6:

 - FIX:  Fixed CGI command line option to use arguments correctly.

See AUP for details.

There is only one thing I can thing of, and that is the script engine.

Older systems where relaxed in spitting out the Status: and
Context-Type: line.   The WEB server will make a default assumption of
302 and Context-Type: Text/Html.

451.5 was enhanced to better support the environment strings,
DOCUMENT_ROOT, and to work out the PHP versions differences, etc.
In short, to better support the CGI standard documented at the Oreilly
Standard CGI Web pages.

My test environment was active perl (2001 version), all versions of PHP
which I remember have different behaviors.

Try adding this to the top of your script:

print "Status: 302\n";
print "Context-Type: Text/Plain\n";
print "\n";

Let me know what you find.

---
Hector

 wrote in message
news:1138899349.40.1138743155@winserver.com...

> My https.dll: 2006-01-31  05:33p (the new gamma), the
> same result, the CGI doesn't work.
>
> I tested it with 451.5 and see that it's the same problem.
> Now I restored an old backup from 454.4 to test it and the
> CGI are working. Didn't you change anything in the 451.5
> update with PHP and CGI? Possibly this has something to do with it.
>
> My ActivePerl version: 5.6.1 Build 635
>
> Perl scripts from a DOS prompt are working, the SpamAssassin from
> wsSpamGuard too.
>
> Rolf