Now WTH is this??

[Silvia Bluejay]

Why do I get this screen at least once every other day? Sometimes it's enough to refresh once and it goes away, other times I have to close the tab and/or the browser and then reload, in order to see the correct page.

 

I don't log out between sessions; the browser is the latest Firefox, Adblock is completely disabled on Basschat, and the operating system is an otherwise all right Win 10.

 

 

[Woodinblack]

Yes, that is exactly when I get it. It is because your cookie has timed out, so it doesn't believe who you are. Actually visiting it refreshes it so it works the second time.

[Woodinblack]

I get that if I click a link to go to basschatfrom my pc upstairs. I mean, it is what it says, the page you requested doesn't exist with the credentials you provided. So for instance if it was a page that isn't publicly viewable it relies on your cookie ID. If that cookie has timed out, then it is right, that page does not currently exist for you.

[BigRedX]

I also get that page from time to time on Safari under Mac OS X 10.13.6.

 

Clicking on the Basschat logo takes me to the home page and still logged in, so for me it's only a minor inconvenience.

[Silvia Bluejay]

Thanks both. I see what you mean, Woody, but that page comes up after I click on my BC bookmark/Favourite on the toolbar, the same one that takes me to normal BC most of the time.

I'm just baffled - and curious - as to why it will periodically decide, between lots of normal sessions on the very same day, that it suddenly can't find the page requested. My bookmark is simply to https://www.basschat.co.uk/ .

[Kiwi]

Is it a browser cache issue?  Have you tried the old CTRL+F5 trick,  Silvia? 

[Silvia Bluejay]

I always do when I refresh, Steve. Sometimes it works, other times it doesn't. This error page is not a nuisance, as it doesn't happen all the time or even often enough to be a problem, but I'm just curious.

[Silvia Bluejay]

Mostly it only works if I close the browser, wait and re-start, so it does sound like, as you say, it's just a cookie issue. Incidentally, I'm rather disappointed at the only partial effectiveness of Ctrl+F5 these days. It used to be able to refresh anything, now it only improves things half of the times at most. Oh, well...

[Woodinblack]

28 minutes ago, Silvia Bluejay said:

I'm rather disappointed at the only partial effectiveness of Ctrl+F5 these days. It used to be able to refresh anything, now it only improves things half of the times at most. 

 

Agreed - I wondered when that became a thing, it used to work well!

[Kiwi]

If you're using Chrome as a browser, cookie management is all going to change next June anyway.