ID: 19295
Comment by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Status: Open
Bug Type: Output Control
Operating System: Solaris 8
PHP Version: 4.2.3
New Comment:
See also bug #19098. Can confirm that workaround posted by
<[EMAIL PROTECTED]> works for me. <[EMAIL PROTECTED]> indicates problem
probably fixed in CVS.
Previous Comments:
------------------------------------------------------------------------
[2002-09-12 19:52:53] [EMAIL PROTECTED]
Specifying an explicit charset in PHP scripts causes the desired header
to be sent:
header( "Content-Type: text/plain" ); # has no effect
header( "Content-Type: text/plain; charset=blah" ); # gets sent
------------------------------------------------------------------------
[2002-09-09 19:20:16] [EMAIL PROTECTED]
Commonplace effects of this problem: formatted monospace text appears
as run-on proportionally-spaced text ('text/html' sent instead of
'text/plain'); Mozilla doesn't recognise stylesheets (requires
'text/css').
------------------------------------------------------------------------
[2002-09-09 19:19:00] [EMAIL PROTECTED]
After browsing CVS diffs, I suspect that this is not
Apache/mod_php4-specific. I see a lot of changes (between 4.2.2 and
4.2.3) in php4/ext/mbstring/mbstring.c and php4/main/SAPI.c.
------------------------------------------------------------------------
[2002-09-08 18:57:49] [EMAIL PROTECTED]
(I recently compiled PHP 4.2.3 for Apache 1.3.26 under Solaris 8 using
gcc 2.95.2 using the same process that I used for PHP 4.2.2. The only
difference is that I also recompiled Apache with a newer version of
mod_perl.)
When using the header( string[, bool[, int]] ) function with a string
parameter of the form "Content-Type: text/...", where "..." is any
valid type that I have so far attempted to use, the response headers
sent by Apache contain only "Content-Type: text/html", or whatever the
default_mimetype is. (I tried changing the default_mimetype in php.ini
and confirmed that it was being used.) If "Content-Type: image/..." is
used (for example) then Apache sends that Content-Type (i.e. only
"text/..." seems to be affected). I am not certain that this is Apache
1.3.26/mod_php4-specific because I have not yet tested with other web
servers. This did not appear to occur in PHP 4.2.2, which is what we
were running last Friday.
./configure --with-apxs=/usr/apache/bin/apxs
--with-config-file-path=/etc/apache --disable-short-tags
--enable-calendar --with-mysql=/usr/local/mysql --with-gdbm=/opt/sfw
--with-tiff=/usr --with-gd=/usr/local --includedir=/usr/local/include
--with-mcrypt --with-java=/usr/java --with-xml --with-tsrm-pthreads
--with-imap=/usr/local/stow/imap-2000c --with-zlib
--with-jpeg-dir=/opt/sfw --with-png-dir=/opt/sfw --with-ttf=/usr/local
--with-t1lib-dir --with-ldap
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=19295&edit=1
