Date: Mon, 24 Feb 1997 20:15:43 +0000 (GMT)
From: Rob Hartill <robh@imdb.com>
To: Apache Mailing List <new-httpd@hyperreal.com>
Subject: Re: META revisited
In-Reply-To: <9702241623.aa18812@gonzo.ben.algroup.co.uk>
Message-ID: <Pine.NEB.3.95.970224201010.8617G-100000@localhost.imdb.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: new-httpd-owner@apache.org
Precedence: bulk
Reply-To: new-httpd@hyperreal.com

On Mon, 24 Feb 1997, Ben Laurie wrote:

> A long, long time ago, I brought up the question of HTTP-EQUIV META tags. I
> was told at the time that this is a client-side thing. However, this does not
> appear to be the case. Firstly, the HTML 3.2 spec clearly says that this tag
> should be used by servers, and secondly, Netscape at least do not process it at
> the client end (as far as I can tell).
> 
> Standards-wise, this is somewhat unfortunate - should this really be in the
> HTTP spec? Anyway, the question is, does anyone have any views? Should we
> support this?

It makes far more sense for the CLIENT to parse the HTML for META
since there's more spare cpu cycles on clients than servers, and the
clients already have to parse the HTML anyway.

Should Apache support it ?, support - yes, as part of the core - no.

It's a trivial module to write (I have one for mod_perl), but it's
definitely not for everyone.