Noting that (of course) we can't actually fix IE, so bar something like reverting to HTTP just for them (Err, yeah... /me barfs), this needs much poking of Microsoft to get something done...

We could double check if our cache-control headers are really making sense everywhere, or if we should make it more flexible etc..

Something else that might be worth investigating is history.pushState magic ?

So tempted to close this INVALID...

declined because we really can't do anything about it and also it's like a duplicate of T55636 which has also been suggested to be -> wontfix