IE9 has a serious problem

Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!

You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:

You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.

xoggoth replied

7 October 2011, 16:06
<meta http-equiv="expires" content="-1" >

Somebody else says that hasn't fixed it. Mind you, she is so technically illiterate she is probably looking at her spin dryer.
Leave a comment:
d000hg replied

7 October 2011, 15:24
The forums other than General are supposed to be for serious discussion, not trolling.
Leave a comment:
petergriffin replied

7 October 2011, 13:35
I have a solution. See sig.
Leave a comment:
d000hg replied

7 October 2011, 11:17
Originally posted by craig1 View Post

IE9 is crap

No it isn't.

Two equally valuable statements.
Leave a comment:
eek replied

7 October 2011, 11:09
Originally posted by xoggoth View Post

eek. Bunged those in at start of page although didn't help but ta anyway.

That code is platform (IIS / asp /asp.net) specific. If you are not running iis you need to whatever equivalent code is required to add those headers to your page.

Next I'd download and run fiddler2 to see what the page is actually doing. That will allow you to check what IE9 is requesting and receiving back (and if indeed it is even requesting a refreshed page).
Leave a comment:
xoggoth replied

7 October 2011, 10:57
eek. Bunged those in at start of page although didn't help but ta anyway.

PS This in the head seems to fix it

<meta http-equiv="expires" content="-1" >

Last edited by xoggoth; 7 October 2011, 11:09.
Leave a comment:
craig1 replied

7 October 2011, 10:37
IE9 is crap with the full-fat version of Outlook Web Access. Unfortunately, only IE runs the full-fat version meaning I had to downgrade the IE on my Win7 VM.

In fact, I can shorten that: IE9 is crap.
Leave a comment:
eek replied

7 October 2011, 10:35
Originally posted by xoggoth View Post

Mentioned before that after updating a webpage and then opening the page in IE I didn't see the changes until I clicked refresh. Seems it's not just me. This is a serious problem if anyone who has ever visited our site and doesn't know about caches, settings etc, is only ever seeing the old pages.

How to get round this. Nevers seems to happen with CUK, so what is in the CUK pages that's not in mine?

Cheers

It sounds like you need to add the proxy-nocache headers stuff to the page but I'm not sure that is the real issue.

HTML Code:

<% Response.CacheControl = "no-cache" %> <% Response.AddHeader "Pragma", "no-cache" %> <% Response.Expires = -1 %>

Is it just internal as it could be that your IT support / infrastructure muppets have things up incorrectly.
Leave a comment:
xoggoth started a topic IE9 has a serious problem

7 October 2011, 09:44
IE9 has a serious problem

Mentioned before that after updating a webpage and then opening the page in IE I didn't see the changes until I clicked refresh. Seems it's not just me. This is a serious problem if anyone who has ever visited our site and doesn't know about caches, settings etc, is only ever seeing the old pages.

How to get round this. Nevers seems to happen with CUK, so what is in the CUK pages that's not in mine?

Cheers
Tags: None