为提升您的使用体验,本站正在维护,部分功能暂时无法使用。如果本站文章无法解决您的问题,您想要向社区提问的话,请到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 提问,我们的支持社区将会很快回复您的疑问。

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

Can't log in after update to 33

  • 1 个回答
  • 1 人有此问题
  • 9 次查看
  • 最后回复者为 cor-el

more options

Hey guys,

a lot of our customers can't log in on our site using Firefox after updating to the newest version (33). It always works in a new private window, and clearing the cookies seems to solve this problem, but most of our users have no clue what cookies are, so asking them to fix this themselves is generally not the best idea.

We wish we wouldn't be forced to tell those users to change Firefox to any other browser, as it's often easier than clearing cookies. So, are there any guidlines of using cookies on a website so it doesn't crash after updating Firefox? Cause maybe we could improve something on our site? Or our only hope is to wait till you guys fix your update process someday?

Thanks in advance!

Hey guys, a lot of our customers can't log in on our site using Firefox after updating to the newest version (33). It always works in a new private window, and clearing the cookies seems to solve this problem, but most of our users have no clue what cookies are, so asking them to fix this themselves is generally not the best idea. We wish we wouldn't be forced to tell those users to change Firefox to any other browser, as it's often easier than clearing cookies. So, are there any guidlines of using cookies on a website so it doesn't crash after updating Firefox? Cause maybe we could improve something on our site? Or our only hope is to wait till you guys fix your update process someday? Thanks in advance!

所有回复 (1)

more options

If clearing the cookies works then maybe look at the code that validates the cookies that Firefox sends to make sure that you ignore and delete the cookie(s) in such a case and make the browser store a new cookie, so it will work on the next login.

A new PB mode window doesn't use the cookies from the regular session, so that would explain this behavior.