So recently, there have been a few occasions where I've just gone to click on a thread or a board or whatever it may be, and instead of navigating me correctly it logs me out. Not particularly sure why this fault is occurring. It happens sporadically. Is anyone else having this issue or is it just me?
I can't think of any scenario in which a thread or board link could plausibly log you out, so my best guess is that it's a cookie/cache issue and your browser is dropping a cookie or something like that.
*Rugby tackles Devin2600 and pedro_collins*
^ Because they copied my signature! And they threw donuts at me! :(
Hi there. I'm sorry for the lack of communcation - though I've continued researching the issue, unfortunately I haven't found anything resembling a solution.
Here is what I wrote on the staff thread about this a couple of weeks ago, which still holds true:
"After some head-scratching, I managed to reproduce this bug. It seems that when browsing ACC with Microsoft Edge, Edge will sometimes send out two requests for the same page, and on the second request, it will pretend not to have any cookies (as if you had never visited ACC before). When ACC receives the cookie-less request, it sets a new session cookie (as it would for anyone who had never visited ACC before). This overwrites the existing session cookie on which you had logged in, so you are logged out.
I haven't discovered any apparent pattern to which pages Edge requests twice. I also haven't observed this behaviour on any other browser. However, I did find multiple bug reports on the Microsoft Edge developer website, some dating back as early as 2016, describing similar issues. Some (for example, this one) are marked "fixed"; others (for example, this one) are not. This, combined with the fact that it also affects other sites, makes me suspect that the root cause of the problem is a long-running bug in Edge that hasn't been properly pinned down by Microsoft's developers yet, and likely won't be for some time to come. So, the most helpful thing we can suggest to users at this juncture is to use a different browser."
I don't like the state this issue has ended up in. I am very much in favour of letting people use whatever browsers or browser-shaped objects they feel like, just on a matter of principle, but in this case I really don't see anything we can do to get it working with Edge. I'm sorry.
There's no place like 192.168.0.0/16.