From:             [EMAIL PROTECTED]
Operating system: Solaris 7 Sparc 64-Bit
PHP version:      4.0.6
PHP Bug Type:     Apache related
Bug description:  POSTs to CGI scripts on Apache 1.3.20 server fail

We recently upgraded our Apache server from 1.3.12 to
1.3.20.  In the process, we also upgraded to mod_perl 1.25
and decided to upgrade PHP from version 3 to version 4.0.6.
After compiling Apache with DSO support, I installed the new
server with the modules. We immediately noticed that every
CGI script (Perl, C compiled, etc) that received a POST
failed after the upgrade.

To test, I created a simple HTML form which posted to the
following Perl script:

***** START test.pl *****
#!/usr/bin/perl -w

use strict;

print "Content-Type: text/html; charset=ISO-8859-1\n\n";

print "<HTML><BODY>\n";

while (my $elem = <STDIN>)
{
  print $elem . "\n";
}

print "</BODY></HTML>\n";
***** END test.pl *****

When tested on an older server, we see:

<HTML><BODY>
recipient=bweldon%40georgefox.edu&subject=brad-test&First_Name=asdf&submit=submit
</HTML></BODY>

When tested on the new server, we see:

<HTML><BODY>
</HTML></BODY>

However, if I comment out from our apache httpd.conf:

LoadModule php4_module        libexec/libphp4.so

the server starts working correctly (with the traditional
behavior for our perl and C compiled CGI scripts). This is a
show-stopper! Please advise on how to fix! Thank you in
advance!

PHP 4.0.6 compiled with:

./configure \
--prefix=/opt/php4 \
--with-apxs=/opt/apache-ssl/bin/apxs \
--with-ldap=/opt/ldap \
--with-mysql=/opt/mysql \
--enable-ftp \
--with-openssl=/opt/openssl \
--with-db2=/opt/BerkeleyDB \
--with-snmp=/opt/ucd-snmp \
--enable-ucd-snmp-hack \
--with-mm=/opt/mm \
--with-sybase=/opt/sybase/openclient \
--without-gdbm \
--enable-sockets


-- 
Edit Bug report at: http://bugs.php.net/?id=11706&edit=1



-- 
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to