[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] Echoed Status and Content-type Problem
- Subject: Re: [cobalt-users] Echoed Status and Content-type Problem
- From: flash22@xxxxxxx
- Date: Fri Mar 9 06:55:18 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
On Fri, 9 Mar 2001, Charles Williams ( CEO ACNS ) wrote:
> Hey all,
>
> I have a weird problem here that maybe somebody out there can shed some
> light on.
>
> If you go to this URL:
> http://www.acns-online.com/chuck/stories/op/storiesView/sid/3/
> you will notice at the top of the page the following output:
>
> Status: 200 OK Content-type: text/html
hmm, looks ok now...or to me
>
> This should not be there. There is a header() call in the redir.php3 script
> as follows:
>
> <snip>
> header("Status: 200 OK");
> </snip>
a newline would help ;)
remember , apache takes your headers plus it's own and merges them, then
starts the content, your missing newline confused it and it glued it's
default content header to your status header...
(There are certain headers that you can't not override btw)
>
> Why is this echoing on the browser screen? Also, the Content-type:
> text/html is nowhere in the scripts and still being echoed.
because php inherently makes the final page text/html , somewhere inside
php it did this for you)
I'm not even gonna ask why you want to send back Status 200 headers ;)
ok, i will ask, you are missing a whole lot of headers that are normally
supplied, you have:
Connected to www.acns-online.com.
Escape character is '^]'.
Status: 200 OK
Content-type: text/html
<html>
---
But normally you'd get all this:
HTTP/1.1 200 OK
Date: Fri, 09 Mar 2001 15:41:23 GMT
Server: Apache/1.3.3 Cobalt (Unix) (Red Hat/Linux)
Last-Modified: Sat, 20 Mar 1999 22:37:50 GMT
ETag: "12802-1bd3-36f4233e"
Accept-Ranges: bytes
Content-Length: 7123
Connection: close
Content-Type: text/html
---
Note that you replied to a HTTP 1.1 request with a HTTP 1.0 reply ;)
among other things, you disabled all cache controlls for the page, didn't
give the poor browser any clue as to download time , and you lied about
connection mode (forcing the browser to assume it *must* close the
connection and reopen it to get the next file)-/
gsh
ps: you have a comment after the <html> ;)
nice resume tho :)