Minichan

Topic: when i go back it doesn't change a thread to having been viewed

squeegee started this discussion 12 years ago #36,935

i actually have to hit the bumps link or reload the page. it used to be that if there were new replies or threads and i viewed them and just used back it would change the thread to having been viewed or it changed the new post count to a new total or whatever. now i go back and it's not been updated like that. it still shows (5 new) or whatever.

r04r joined in and replied with this 12 years ago, 2 minutes later[^] [v] #501,387

I don't think anything changed on our side, unless something has somehow been configured differently when moving to the new server but php is set to not cache, so that'd be odd. It could be your browser is caching the pages, but it'd also be odd if that suddenly changed.

squeegee (OP) replied with this 12 years ago, 9 minutes later, 11 minutes after the original post[^] [v] #501,389

@previous (r04r)
i checked and my browser is not cashing anything. sounds like the problem is on your end.

r04r replied with this 12 years ago, 6 minutes later, 17 minutes after the original post[^] [v] #501,390

@previous (squeegee)
I'm not so sure, mostly because I don't experience the issue myself (when i back out of this topic the seperator bar still shows when something new has been posted since, and everything above it is indeed new), and the index returns the following headers:

Cache-Control:max-age=1, private, must-revalidate
Pragma:no-cache
Expires:Thu, 19 Nov 1981 08:52:00 GMT

Which should make it so that it never gets cached by the browser. What browser are you using, and what version?

squeegee (OP) replied with this 12 years ago, 5 minutes later, 23 minutes after the original post[^] [v] #501,392

@previous (r04r)
actually i first noticed it on my phone, which is an android and i'm using the default browser. on my desktop here i'm using FF 32.0.3

it does it on both

(Edited 18 seconds later.)

r04r replied with this 12 years ago, 1 minute later, 24 minutes after the original post[^] [v] #501,393

@previous (squeegee)
When did it start happening?

squeegee (OP) replied with this 12 years ago, 1 minute later, 26 minutes after the original post[^] [v] #501,394

@previous (r04r)
it's also doing it on an ipad air on the default browser.

I think it started doing it after the move. it's only been very recently that the issue started.

Anonymous C joined in and replied with this 12 years ago, 1 minute later, 27 minutes after the original post[^] [v] #501,395

@501,392 (squeegee)
You shouldn't use the default android browser. Didn't you read r04r's warning?

squeegee (OP) replied with this 12 years ago, 54 seconds later, 28 minutes after the original post[^] [v] #501,396

@previous (C)
i'm using a safe one. from what i understand the latest version is not vulnerable.

r04r replied with this 12 years ago, 2 minutes later, 30 minutes after the original post[^] [v] #501,397

I've actually just managed to replicate this in chrome as well, though it's spotty. I'll look into it further later and see if I can do anything about it (though I am skeptical), thanks for letting me know though.

squeegee (OP) replied with this 12 years ago, 3 minutes later, 33 minutes after the original post[^] [v] #501,398

@previous (r04r)
sure thing, thanks for looking into it

r04r replied with this 12 years ago, 3 days later, 3 days after the original post[^] [v] #501,801

@previous (squeegee)
fixed?

squeegee joined in and replied with this 12 years ago, 1 minute later, 3 days after the original post[^] [v] #501,802

@previous (r04r)
yup. works like a charm now.

r04r replied with this 12 years ago, 39 seconds later, 3 days after the original post[^] [v] #501,803

@previous (squeegee)
ok sorry about that!

squeegee replied with this 12 years ago, 1 minute later, 3 days after the original post[^] [v] #501,804

@previous (r04r)
no problem at all. thanks for correcting it. it was only a minor annoyance, i appreciate you working on it
:

Please familiarise yourself with the rules and markup syntax before posting.