[Zope] Does Zope translate http-equiv statements?

Thu, 14 Feb 2002 09:37:59 -0800

Andreas and Lennart,

Excuse me if perhaps I'm misunderstanding you and you already know this.. but..

"The part between <HEAD> and </HEAD>" isn't the same as what most 
people mean when they refer to the "header" actually..

  The 'header' of an HTML document is rarely seen, unless you can sit 
and watch the streamed exchange of data between the client and server 
directly.. (using special tools, - sometimes this is *quite* useful 
in debugging an interaction..)

   It's in the "real" (almost always unseen) header that the client 
makes the "GET" statement and it's also where the exchange that 
determines mime-types happens.. It's also where you might get 
commands such as a redirect or a 404 not found..(or other response 
codes..)

<dtml-call "RESPONSE.setHeader ...  DOES effect the stuff that 
happens in the "real" header, and that's why it's such a useful 
command..

The stuff in the HEAD can frequently be ignored if it contradicts 
something in the real header.. This is the thing that varies by 
browser..

Take a look at the HTTP specification.. it's all in there, and more..

Hope that helps!

Chris Beaumont

>----- 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
>