From:             [EMAIL PROTECTED]
Operating system: RedHat Linux 6.0(ish)
PHP version:      4.0.6
PHP Bug Type:     Output Control
Bug description:  Headers output in HTML body.


Sorry if this is a duplicate (I've checked and it doesn't look like it
though), or me being silly...

We've had this problem in versions 4.0.4pl1 through to PHP4.0.6, running as
a CGI through apache (various versions between 1.3.3 and 1.3.12 I think...)
using the setup described in the PHP docs.

Configure options approximately (they have changed through various versions
of PHP I've compiled up)

./configure --with-mysql --with-gd --enable-force-cgi-redirect
--with-config-file-path=/etc/php4/cgi/ --with-imap --enable-ftp
--with-openssl --with-kerberos=/usr/kerberos --with-zlib-dir=/usr/lib
--with-jpeg=/usr --with-tiff=/usr

The systems that PHP are running on are some 20 patched-up RH6.0 machines,
all of which exhibit this symptom.

It can be got around by disabling loading of any dynamic modules, even
dynamic modules which don't exist on the server cause this problem if you
attempt to load them with an "extension=" line in the relevant php.ini.

I'd previously assumed it to be specific to the mysql module or similar,
but it seems that it's the module loading routine which is erroneously
outputting a newline or two to indicate the end of the HTTP headers before
it should do, because if you try to load a module that doesn't exist it
still does the same.

I'm reporting it now because I have just got a new bit of information, and
nobody could have reported it yet otherwise I assume you would have solved
it in php-4.0.5.



PS. Some system info. Just ask if you need more that this...

Linux version 2.2.13 ([EMAIL PROTECTED]) (gcc version
egcs-2.91.60 19981201 (egcs-1.1.1 release)) #1 SMP Mon Dec 13 01:50:21 GMT

Red Hat Linux release 6.0 (Hedwig)

Server version: Apache/1.3.9 (Unix)
Server built:   Dec 13 1999 17:18:12

Edit bug report at:

PHP Development Mailing List <>
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