Reply to Re: IE doesn't honor Cache-control with location.href= calls

Your name:

Reply:


Posted by Jure Erznoznik on 09/30/86 11:24

Well, / represents a login screen when user is not logged in yet and main
app window when he is.
The problem occurs when I login, logout (which shows me the login screen
again) and then press "Cancel" button, which has location.href="/" OnClick
event. What I get is the app content from when i was logged in. Pressing
refresh of course shows the login screen again since the user is not logged
in.

Thanks for any feedback,
Jure

"Neredbojias" <neredbojias@neredbojias.com> wrote in message
news:MPG.1d623c4c7db9b37e989742@news.intergate.com...
> With neither quill nor qualm, Jure Erznoznik quothed:
>
>> I make sure that all my pages have the Last-Modified and Cache-control
>> headers:
>>
>> Last-Modified: Mon, 08 Aug 2005 12:08:25 GMT
>> Cache-control: max-age=86400, must-revalidate
>>
>> While this works well for links and back button in IE 6.0, it fails for
>> Javascript location.href = "/" statement.
>> The cache-control header is provided so that IE doesn't squeak about page
>> being expired when the user presses the back button.
>>
>> Does anybody know how to get around this?
>>
>> Thanks,
>> Jure
>
> What fails? If you go to "/", how does the current page expiration come
> into play?
>
> --
> Neredbojias
> Contrary to popular belief, it is believable.

[Back to original message]


Удаленная работа для программистов  •  Как заработать на Google AdSense  •  England, UK  •  статьи на английском  •  PHP MySQL CMS Apache Oscommerce  •  Online Business Knowledge Base  •  DVD MP3 AVI MP4 players codecs conversion help
Home  •  Search  •  Site Map  •  Set as Homepage  •  Add to Favourites

Copyright © 2005-2006 Powered by Custom PHP Programming

Сайт изготовлен в Студии Валентина Петручека
изготовление и поддержка веб-сайтов, разработка программного обеспечения, поисковая оптимизация