HTTP-EQUIV in META

Luke Y. Lu (ylu@mail.utexas.edu)
Thu, 9 Feb 95 20:40:58 EST

Hi,

I tried to use
<META HTTP-EQUIV="Location" CONTENT="the new URL"> in the <HEAD> of
a document to redirect the client to the new URL. It does not work
with NCSA httpd 1.3.

The HTML 2.0 DTD (http://www.oac.uci.edu/indiv/ehood/html2.0/DTD-HOME.html)
is not very clear at this point. It only indicates that "It is recommended
that servers ignore any META elements which specify HTTP-equivalents which
are equal (case-insensitively) to their own reserved response headers". I
believe it's perfectly legitimate and logical to use the http-equiv to
specify the Location header (quite a few cgi scripts use it anyway), since
it's much more elegant (require much less sysadmin) than the
edit-server-config-file-to-add-redirect-and-restart-the-server-or-send-
a-signal-to-have-the-server-re-read-the-config process. I was wondering if
any existing server support this feature. If not, why?

Any suggestions/comments appreciated. TIA,

__Luke

--
Luke Y. Lu
mailto://ylu@mail.utexas.edu
http://www.utexas.edu/~lyl/