16-10-2024 03:52 AM
Hi!
I'm Rivindhu. I'm developing a python Django website and I test the website locally by using Firefox developer edition. In my website there's a login system. Whenever I tried to login a user It's not login the user sometimes. But sometimes user login succeeded sometimes not. And If the user is logged in when I press a random button in the website. Then the website is displaying like I'm not logged in.
I have tried this several times. And my login credentials are correct. And this is only happened with the Firefox developer browser. But the login system and the website is working fine with the regular Firefox browser, chrome browser, and the edge browser as well.
I'm waiting for your response.
01-09-2026 02:57 PM
@Rivindhu wrote:Hi!
I'm Rivindhu. I'm developing a python Django website and I test the website locally by using Firefox developer edition. In my website there's a login system. Whenever I tried to login a user It's not login the user sometimes. But sometimes user login succeeded sometimes not. And If the user is logged in when I press a random button in the website. Then the website is displaying like I'm not logged in.
I have tried this several times. And my login credentials are correct. And this is only happened with the Firefox developer browser. But the login system and the website is working fine with the regular Firefox browser, chrome browser, and the edge browser as well.
I'm waiting for your response.
I also have the same question, because intermittent login behavior like this is particularly confusing when the exact same Django application works normally in other browsers. If the credentials are definitely correct and the login succeeds sometimes but then appears to disappear after clicking another button or navigating to another part of the site, I would be curious whether Firefox Developer Edition is handling the session or cookies differently from the regular Firefox release. Since the issue seems limited to the Developer Edition, it makes me wonder if a browser setting, privacy feature, cookie policy, cached session information, or some developer-specific configuration could be interfering with Django's session cookie. The fact that the user can appear logged in initially and then suddenly be treated as anonymous after another action makes the session persistence part especially worth checking rather than focusing only on the authentication credentials themselves.