搜索 | 用户支持

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

Learn More

authentication cookie missing for <1% of firefox users

  • 3 个回答
  • 4 人有此问题
  • 54 次查看
  • 最后回复者为 zeroknight

more options

On our online application we are facing with some strange behavior for a small percentage of our firefox users (<1%).

When doing oauth2 authorization, after generation of the authentication token we redirect to another platform but we are detecting that for a small percentage of Firefox the cookie (my_auth_cookie) with the auth token is not present.



GET: https://www.mywebsite.com/application/login Response:

new location https://www.mywebsite.com/otherapplication/redirect


set-cookie: my_auth_cookie expires=Mon, 04 Dec 2023 13:49:15 GMT; domain=.mywebsite.com; path=/; secure; samesite=lax; httponly


      2. GET https://www.mywebsite.com/otherapplication/redirect
          Set-cookie: mycookie: value
          Host: www.mywebsite.com


In cookie tab I see my_auth_cookie (value: xxxx, domain: .mywebsite.com, expires: Mon, 04 Dec 2023 13:49:15 GMT, httponly: checked, secure: checked,SameSite: Lax, partitionkey: empty, Priority: medium



I’ve tried to replicate but without success (with multiple extensions, including multi-account containers), with multiple configurations of Total Cookie Protection.

Again, this only seems to be happening to a very limited number of firefox users but for these, it happens 100% of the time. We see it occurring for versions 119 and 120 but now and then for older versions.

Feedback reports no extensions&addons.


Any ideas on what we could be dealing with? Any help would be greatly appreciated.

On our online application we are facing with some strange behavior for a small percentage of our firefox users (<1%). When doing oauth2 authorization, after generation of the authentication token we redirect to another platform but we are detecting that for a small percentage of Firefox the cookie (my_auth_cookie) with the auth token is not present. GET: https://www.mywebsite.com/application/login Response: new location https://www.mywebsite.com/otherapplication/redirect set-cookie: my_auth_cookie expires=Mon, 04 Dec 2023 13:49:15 GMT; domain=.mywebsite.com; path=/; secure; samesite=lax; httponly 2. GET https://www.mywebsite.com/otherapplication/redirect Set-cookie: mycookie: value Host: www.mywebsite.com In cookie tab I see my_auth_cookie (value: xxxx, domain: .mywebsite.com, expires: Mon, 04 Dec 2023 13:49:15 GMT, httponly: checked, secure: checked,SameSite: Lax, partitionkey: empty, Priority: medium I’ve tried to replicate but without success (with multiple extensions, including multi-account containers), with multiple configurations of Total Cookie Protection. Again, this only seems to be happening to a very limited number of firefox users but for these, it happens 100% of the time. We see it occurring for versions 119 and 120 but now and then for older versions. Feedback reports no extensions&addons. Any ideas on what we could be dealing with? Any help would be greatly appreciated.

所有回复 (3)

more options

有帮助吗?

more options

Hi, thank you for your reply. We tried multiple configurations of total cookie protection and could not replicate. Feedback from clients is that no specific configurations were used - so we are assuming default values.

有帮助吗?

more options

Defaults can vary due to rollouts, you can see active ones by visiting about:studies.

有帮助吗?

我要提问

您需要登录才能回复。如果您还没账号,可以提出新问题