Re: Sending raw headers

At 11:55 30.6.2000 +0300, you wrote: <snip>

What in the world are you talking about? I have yet to see a 404 Page that is not text/html. It could be an image/gif, I suppose, but you are always going to have a content-type for the error description.

404 yes, but 202 no, and because of the Content-Type PHP sends, you get a nice popup with "page contain no data", as if that was not the exact intention. Why should we bother? Take a web based chat : if you are able to submit a form and return no data, you can `keep' the form unchanged. Or, if you are doing some time consuming operations, you can send a "Location" header to make a redirect to another page.

Ah, at least someone who figures what I'm talking about :). Yes, webchat is exactly what I'm developing. It works nicely with redirections also but naturally is not as fast as it could be (and we're not satisfied until it's perfect, right?). I tried many different ways to do the headers, cgi version with -q parameter, etc. Doesn't work because -q denies _all_ headers (says "headers already sent in blabla.php in line 2). simply by echoing the Status:204 won't work. I wonder how hard it would be to patch the sources so php wouldn't send the content-header if special headers are sent before it.. You wouldn't know any workaround on this btw? -Timo