NEW USERS - HOW TO REGISTER!

[SunsRIt]

It’s like the keep me logged in button isn’t working.

[Superbone]

It’s like the keep me logged in button isn’t working.

Yep. Something has changed in the forum code. (Well, could be a Safari change too, I suppose.) It was working fine until recently. A funny thing happening now is I can refresh the page and it will show me logged in and your new post and when I click on the flag to go to latest, I'm sitting on the first post now and logged out. Definitely Safari specific as Firefox hasn't logged me out once since keeping a parallel page open on it.

[SunsRIt]

It’s like the keep me logged in button isn’t working.

Yep. Something has changed in the forum code. (Well, could be a Safari change too, I suppose.) It was working fine until recently. A funny thing happening now is I can refresh the page and it will show me logged in and your new post and when I click on the flag to go to latest, I'm sitting on the first post now and logged out. Definitely Safari specific as Firefox hasn't logged me out once since keeping a parallel page open on it.

I just moved around between threads without going to the flag to go to the last post and it worked fine. If I do use the flag it logs out and I have to sign in again. I also have to log back in when I go back to the site after using other apps on my phone.

[Mori Chu]

Okay, I have made some changes to the server settings that I think may help, based on some info I read today.

For the nerds in here, some details: I think it has to do with top-level vs subdomain cookies. When you log in to this site or many others, the site leaves a cookie in your browser with some info about your login. Our site is on the domain www.phx-suns.net, but the cookie was being set on the top-level domain name of just phx-suns.net. In theory that would be just fine; a cookie on the top-level domain is meant to cover all subdomains under it. But recent best practices in web security recommend not using this feature because it can allow a malicious cookie set in one place to possibly affect another place, particularly sites that have a bunch of subdomains, such as sites where each user gets a subdomain called e.g. myusername.example.com.

Anyway, from my reading, recent versions of Safari have started to block cookies unless the cookie has EXACTLY the same domain name as the site. So a cookie set on just phx-suns.net would not be allowed or found when going to www.phx-suns.net. That's why the site would think you were logged out. There may have been another issue related to cookies and http vs https protocol, but I am not positive.

I made a change so that the cookies will be set on www.phx-suns.net securely, and I hope this will help. I think Safari is the only browser to strictly enforce this kind of cookie-blocking behavior by default, but others will likely follow. So it's good to try to get it fixed now before other folks start seeing issues.

TL;DR - I think I may have fixed the issue by tweaking the board settings. For those who were having problems in Safari: after logging in this afternoon (later than 3:05pm AZ time), do you still see the issue? Let me know. Thx.

[Superbone]

Awesome! That makes sense to me and why it was logging us out in the middle of a session when changing threads.

[SunsRIt]

I appreciate your efforts. I just used the flag to go to the last read and it logged me right out.

[Superbone]

I appreciate your efforts. I just used the flag to go to the last read and it logged me right out.

Have you tried clearing your cache for the site? So far, so good for me. Just used the flag and it worked like it's supposed to.

ETA: And as soon as I say that, I go to a new post on another thread and it logged me out and took me to the first post.

[pickle]

Yep I also just got logged out again too.