[Zope] Does Zope translate http-equiv statements?

Andreas Jung Andreas Jung" <andreas@zope.com
Thu, 14 Feb 2002 11:20:40 -0500


----- Original Message -----
From: "Lennart Regebro" <lennart@regebro.nu>
To: "Andreas Jung" <andreas@zope.com>; <zope@zope.org>
Sent: Thursday, February 14, 2002 11:12
Subject: Re: [Zope] Does Zope translate http-equiv statements?


> From: "Andreas Jung" <andreas@zope.com>
> > What is a HTML header ?
>
> You know, the part between <HEAD> and </HEAD>... :-)
>
> > I assume you mean meta-tags ?!
>
> I do, yes.
>
> > Zope does not care about http-equiv statements. Why should it ?
>
> No reason at all, really. Some servers do and I'm trying to figure out
> wether it is IE6 or the w3.org P3P validator that has a bug, and in that
> case which bug it is. The P3P validator is happy with this statement:
>
> <meta http-equiv="P3P" content="CP='CAO DSP COR LAW IND UNI COM NAV CURa
> ADMa DEVa OUR'">
>
> IE6 does not like it, but they both like:
> <dtml-call "RESPONSE.setHeader('P3P','CP=' + _.chr(34) + 'CAO DSP COR LAW
> IND UNI COM NAV CURa ADMa DEVa OUR' + _.chr(34) )">
>
> Now, as you see, there are two differences here. One is an http-equiv, and
> the other is that the single and double quotes are switched.

HTTP-equiv is only for the web client. In your case I would slap the guys
from M$ for yet-another-non-compliant-implementation.

Cheers,
Andreas