Received: by taz.hyperreal.com (8.8.4/V2.0) id JAA14202; Mon, 24 Feb 1997 09:37:55 -0800 (PST) Received: from eastwood.aldigital.algroup.co.uk by taz.hyperreal.com (8.8.4/V2.0) with SMTP id JAA14122; Mon, 24 Feb 1997 09:37:45 -0800 (PST) Received: from gonzo.ben.algroup.co.uk (gonzo.ben.algroup.co.uk [193.133.15.1]) by eastwood.aldigital.algroup.co.uk (8.6.12/8.6.12) with SMTP id RAA08130 for ; Mon, 24 Feb 1997 17:37:27 GMT Subject: META revisited To: Apache Mailing List Date: Mon, 24 Feb 1997 16:23:05 +0000 (GMT) From: Ben Laurie X-Mailer: ELM [version 2.4 PL24 PGP2] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-ID: <9702241623.aa18812@gonzo.ben.algroup.co.uk> Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@hyperreal.com 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? Cheers, Ben. -- Ben Laurie Phone: +44 (181) 994 6435 Email: ben@algroup.co.uk Freelance Consultant and Fax: +44 (181) 994 6472 Technical Director URL: http://www.algroup.co.uk/Apache-SSL A.L. Digital Ltd, Apache Group member (http://www.apache.org) London, England. Apache-SSL author