I have forgotten the exact details, but some time back I found it
necessary to pad out the body of the redirect page in order to make IE
perform as intended. It may have been for an older version of IE, and
the padding just needed to be a certain number of bytes. I think I came
across a later reference to the problem. Have you googled for info?
Padding follows.
Cliff
<!--
Testing an unusual feature of IE
xxxxxxxxxx xxxxxxxxxx xxxxxxxxxxx xxxxxxxxxx xxxxxxxxxx xxxxxxxxx xxxxxxxxxx
xxxxxxxxxx xxxxxxxxxx xxxxxxxxxxx xxxxxxxxxx xxxxxxxxxx xxxxxxxxx xxxxxxxxxx
xxxxxxxxxx xxxxxxxxxx xxxxxxxxxxx xxxxxxxxxx xxxxxxxxxx xxxxxxxxx xxxxxxxxxx
xxxxxxxxxx xxxxxxxxxx xxxxxxxxxxx xxxxxxxxxx xxxxxxxxxx xxxxxxxxx xxxxxxxxxx
xxxxxxxxxx xxxxxxxxxx xxxxxxxxxxx xxxxxxxxxx xxxxxxxxxx xxxxxxxxx xxxxxxxxxx
xxxxxxxxxx xxxxxxxxxx xxxxxxxxxxx xxxxxxxxxx xxxxxxxxxx xxxxxxxxx xxxxxxxxxx
xxxxxxxxxx xxxxxxxxxx xxxxxxxxxxx xxxxxxxxxx xxxxxxxxxx xxxxxxxxx xxxxxxxxxx
xxxxxxxxxx xxxxxxxxxx xxxxxxxxxxx xxxxxxxxxx xxxxxxxxxx xxxxxxxxx xxxxxxxxxx
xxxxxxxxxx xxxxxxxxxx xxxxxxxxxxx xxxxxxxxxx xxxxxxxxxx xxxxxxxxx xxxxxxxxxx
xxxxxxxxxx xxxxxxxxxx xxxxxxxxxxx xxxxxxxxxx xxxxxxxxxx xxxxxxxxx xxxxxxxxxx
xxxxxxxxxx xxxxxxxxxx xxxxxxxxxxx xxxxxxxxxx xxxxxxxxxx xxxxxxxxx xxxxxxxxxx
-->
Marco Bizzarri wrote:
Ok, I've been able to experiment. All my pages have the following in
the <head> section:
<meta http-equiv="Cache-Control" content="no-cache">
<meta http-equiv="Pragma" content="no-cache">
<meta http-equiv="Expires" content="Date.Now">
<meta http-equiv="Pragma-directive" content="no-cache">
<meta http-equiv="cache-directive" content="no-cache">
Also, I added, before every redirect, the following:
request.get('RESPONSE').setHeader('pragma', 'no-cache')
Any suggestion?
On 5/31/06, Kees de Brabander <[EMAIL PROTECTED]> wrote:
Either
<dtml-call "RESPONSE.setHeader('pragma','no-cache')">
or
<dtml-call "RESPONSE.setHeader('Expires',(_.DateTime()-1).rfc822())">
or both in the head section of your page will do the trick.
cb
----- Original Message -----
From: "Marco Bizzarri" <[EMAIL PROTECTED]>
To: "Zope Users Mailing List" <zope@zope.org>
Sent: Wednesday, May 31, 2006 7:33 AM
Subject: [Zope] Internet Explorer does not follows redirect,while Firefox
does
> Hi all.
>
> I don't think this is a specific Zope problem. However, I'm
> experiencing it in a Zope context, and this is why I'm here asking.
>
> In a custom Zope application, we have a problem with Internet Explorer.
>
> The application follows a "page -> submit -> redirect -> page" cycle.
>
> To state more clearly: the page presented to the user can have a link.
> When the user clicks on the link, something is done, and eventually
> the user is redirected to the same page which will display different
> data based on the results of its previous click.
>
> The problem is that when IE sees that the result page has the same URL
> as the first page it does not reload the page and instead shows me
> the cached version.
>
> The problem is not shown with Firefox.
>
> As far as I can understand, this is an HTTP header issue, but I would
> like to know if anyone already has experienced this problem, and has
> some solution about it.
>
> Regards
> Marco
> --
> Marco Bizzarri
> http://notenotturne.blogspot.com/
> _______________________________________________
> Zope maillist - Zope@zope.org
> http://mail.zope.org/mailman/listinfo/zope
> ** No cross posts or HTML encoding! **
> (Related lists -
> http://mail.zope.org/mailman/listinfo/zope-announce
> http://mail.zope.org/mailman/listinfo/zope-dev )
>
_______________________________________________
Zope maillist - Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope-dev )
