going to new post in chrome - endless page reloading

Anyone else have this problem with chrome? When i get a new post notification and click the link to go to the new post, it doesn't actually display the new post. It instead is showing me a cached version of the page. And the page just keeps reloading over and over again. I have to click on a link to stop the endless reloading.

Usually i just remove the bookmark bit at the end of the url: #post535568 and then get the page to load correctly including loading the updated content. I have the same caching issue with the index of posts. This post right now wont show up for me when i go back to the chillout index of posts.

I assume this is some compatibility issue with the forums and chrome - i dont usually have any caching issues with other sites.

thanks

I use chrome and this never happens for me.

hmm, what version? are you running 4.x?

I do not have this issue either. I'm also using the latest dev version of Chrome, build 4.0.302.3

weird - it's working for me now at home, but at home my chrome is on the beta channel so it's a bit newer then the one i had at work.

I use stable, 4.0.249.78

very weird. I cant even login properly using chrome. I just went to a thread i'm subscribed to that had a new post. I wasn't logged in. I clicked the reply button, got the login prompt, put in my info and got the thank's for logging in message and then it bounced me back to the login page. Tried logging in a few times with the same results.

I go back to the thread and try to reply and get the login page again. This time when i login i click on my control panel and then click to go to this thread, where it now says i'm logged in. If i go back to that first thread, it'll act like i'm not logged in. If i go to the home page, it'll act like i am not logged in.

Something really weird is going on. Even if google has a cached copy of the page, when i try to reply it should see my login cookie and let me reply ( i assume).

I wonder if we're using some sort of proxy at work that's mucking things up somehow.

ok nevermind - it's not just chrome. IE is behaving in the same weird way as well. There must be some odd proxy issue going on with whatever my work network is using.