Headers are actually visible in the browser?!?!?

MadMikey

I've just run into this strange problems. Headers that are sent from my site are actually being displayed in the browser (this is totally messing up the gzip compression). Any ideas what could be causing this? For example:

With HTTP 1.1 enabled in my browser, I receive this for every page:

X-Powered-By: PHP/4.2.2 Set-Cookie: ; path=/; domain=.domain.net Set-Cookie: bblastvisit=1055581677; expires=Sun, 13-Jun-04 09:07:57 GMT; path=/; domain=.domain.net Set-Cookie: bblastactivity=1055581677; expires=Sun, 13-Jun-04 09:07:57 GMT; path=/; domain=.domain.net Content-Encoding: gzip Content-Length: 4187 Content-type: text/html ...........followed by gzipped garbage.

With HTTP1.1 turned off, it looks like this:

TheIceman5

probably missing a > somewhere

robotspacer

I'm having this problem also. I'm not using gzip compression though, so the pages end up like the attachment. Here's the part that's confusing me though: It's not consistent. When it happens, all I do is refresh the page, and it's fine.

I'm not seeing any problems in my code, and I don't see how a missing bracket could be a problem if it's inconsistent anyhow. Any other ideas?

Weedpacket

My suspicions focus on the server; PHP doesn't care if the browser is making requests as per HTTP1.0 or HTTP1.1.

MadMikey

I had totally forgotten about this thread.

This problem was happening on a brand new server from RackShack.net. After trying to figure it out for a couple of days, I just asked them to restage the server. Only cost me 29.99 and only took them 45 minutes.

On the newly restaged server, there were no problems with PHP whatsoever.

I guess this just reinforces the phrase: "If it can't be done with a phone call and a checkbook, it can't be done."

robotspacer

Interesting.

Something worth noting is that in my case, it seems to happen the most on pages that use MySQL the most.