Sending HTTP response headers causes errors

[Peter Gaunt]

I'm in the process of moving my site from one server to another (my old
hosting company appears to have gone bust).

On the old host and on my local Mac OS X machine I can send HTTP/1.1
response headers with no problem (e.g. header( 'HTTP/1.1 200 OK' ).

If I do the same on the new server I get redirected to the server's
'Internal Error' page (i.e. error 500). No indication of what the error
is.

All three servers are running PHP/4.1.2 and either Apache 1.3.26 or
1.3.27.

It appears that the new server does not like me calling header() with
any string without a colon. If do header('Henry Horse') it also causes
an error. The other servers don't. Equally, if I put a colon in the
HTTP header it also doesn't cause an error (though the header is then
meaningless).

I have no control over httpd.conf or what modules are installed. I do
have access to .htaccess. I also have no access to the error log.

Anyone got any idea what's causing this and is there a way around it?

--
Pete
====
*** Email is pete -at- dawnsun -dot- net

[Billy Harvey]

In article <20************ *********@email .in.my.sig>,
Peter Gaunt <pe**@email.in. my.sig> wrote:

I'm in the process of moving my site from one server to another (my old
hosting company appears to have gone bust).

On the old host and on my local Mac OS X machine I can send HTTP/1.1
response headers with no problem (e.g. header( 'HTTP/1.1 200 OK' ).

If I do the same on the new server I get redirected to the server's
'Internal Error' page (i.e. error 500). No indication of what the error
is.

All three servers are running PHP/4.1.2 and either Apache 1.3.26 or
1.3.27.

It appears that the new server does not like me calling header() with
any string without a colon. If do header('Henry Horse') it also causes
an error. The other servers don't. Equally, if I put a colon in the
HTTP header it also doesn't cause an error (though the header is then
meaningless) .

I have no control over httpd.conf or what modules are installed. I do
have access to .htaccess. I also have no access to the error log.

Anyone got any idea what's causing this and is there a way around it?

--
Pete
====
*** Email is pete -at- dawnsun -dot- net

Pete,

Apache may be configured on the failing server to override specific headers.
You should be able to work around this by prefixing your 'HTTP...' header
with 'Status: HTTP/1.1 200 OK'.

Billy

[Peter Gaunt]

In article <pp************ @kudzu.thrillse eker.net>, Billy Harvey
<Bi**********@t hrillseeker.net > wrote:

In article <20************ *********@email .in.my.sig>,
Peter Gaunt <pe**@email.in. my.sig> wrote:

I'm in the process of moving my site from one server to another (my old
hosting company appears to have gone bust).

On the old host and on my local Mac OS X machine I can send HTTP/1.1
response headers with no problem (e.g. header( 'HTTP/1.1 200 OK' ).

[snip]
Apache may be configured on the failing server to override specific headers.
You should be able to work around this by prefixing your 'HTTP...' header
with 'Status: HTTP/1.1 200 OK'.

I tried that. Worked in some cases and not others.

I've now discovered a difference between the three servers. My old
server and my local server are configured to run PHP as an Apache
module. The new one is configured to run it as a CGI module. If I add
'RemoveHandler .php' to the .htaccess file on the new server, PHP then
runs as an Apache module there too and the problems with the headers go
away. I haven't the faintest idea why this should be. Anyone?

Running as an Apache module also has some side-effects. When I moved the
site the server_signatur e variable (and one or two others) vanished.
Now with PHP running as an Apache module they've reappeared.

--
Pete
====
*** Email is pete -at- dawnsun -dot- co -dot- uk