I think this is a bug, but not sure… when setting up hotspot in 2.9beta15 I am able to make it work mostly, but when a user logs in, and the explicity clicks LogOut they are not logged out. A hotspot user can continue to use the internet with no restrictions. Clicking LogIn no longer asks for a user/pass either - it simply bounces between the login and logout page. I am guessing there is a cookie set and its not erasing it?
I believe so. I think what is happening is the cookie that the client has is not expiring and the server is just accepting it as a valid connection - or the cookie on the server is not expiring. When I am in there today I will double check which one is not getting deleted.
I am now running 2.9beta16 and this is still a problem… or maybe its programmed that way and needs to be looked at. When logging into the hotspot I am assuming a cookie is placed in the clients browser. When you explicitly click LOGOUT the session is removed, but the next attempt to browse the net the hotspot server consumes the browsers cookie and auto-logs the user in. If they click LOGOUT, they should have to log in again with manual credentials, not automatically log in. Can this be fixed?
I have loaded 2.9 RC1 and still see this problem. Can this be fixed for the final release so we do not need to keep going into STATUS.HTML and adding ‘?erase-cookie=true’ ?
I have the same issue but modifying the status.html file doesn’t work. But if I remove the cookie from the router they have to successfully enter their credentials again. I disabled cookies login-by for now, but I need to use them
Thank you