On 30 Aug 2000, at 5:55, Eko Priono wrote:
> > AFAIK There is no correct way to interpret the meta
> > http-equiv, since its not part of any HTML spec. I don't
> > know enough http to tell if this is legal in the http header.
> > (ie put "Refresh: 60" along with the "Content-type: text/html")
>
> HTML *not* the same as HTTP ! Two different things !! ;)
> You don't put META-refresh, in HTTP header, but in the page's
> HTML header section (Altough I currently put some HTTP header
> line as META tags -- the other way around ;-)
Yes but the HTML tag is "HTTP-EQUIV"!! What goes there should
be made look like it was in the HTTP headers.
Like I said (meant), the Refresh would fall under HTTP, but to get it
one uses HTML tag.
There are some places I use something like this -
http://gimpstein.virtualave.net currently HTTP redirects to
http://www.connect.usq.edu.au/students/q9821823/gimpstein.html
but this is set to change, when I bring the interactive things in.
[BTW virtualave have stuffed up a few things with the scripts:
Content-type: text/plain no longer works - comes out as text/html.]
You might have seen FrontPage etc put Encoding (or something
similar) into a http-equiv; this is so the browser can display the
correct charset without bothering the server.
