Re: Sending raw headers

Hi Rasmus! On Fri, 30 Jun 2000, Rasmus Lerdorf wrote: > > You're propably doing it right but php sends the useless content-type > > header even when you send your own headers. It might be within standards > > but if most of the browsers dont understand it, i consider it useless.. :| > > Tell me too if you find a way around this 'feature'. Same problem when you > > use eg. "Status: 204" header. There was a bugreport in php.net but as far > > as I know nobody's doing nothing about it. > > 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. -- teodor