Our users are experiencing HTTP 431 error codes sporadically which is stopping them from logging in. The error is caused by too many Auth0 cookies as the don’t appear to be cleared when logging out. I can’t replicate the error on my local dev environment, but it does occur on both staging and produ…

Having the same issue here. Any news on this one?

Unfortunately no. Definitely related to the cookies not being cleared, just appended…

Did anyone ever resolve this? We’re seeing the same thing.

Hi, We’re getting the same error intermittently. Does anyone have a solution?

Hey there folks! Let me research that hurdle for you and get back to you once I have any info on that front.

Hey there guys! I’ve got one more question from our engineering team before they start digging into that. Is any of you experiencing the same thing but not hosting on AWS and CloudFront? We need to make sure that the obstacle in on our side of stack. Thank you!

Hey there! Have anyone of you got a chance to check my previous message?

Ping ping friendly ping :slight_smile:

Cookies not cleared on logout causing http 431 errors

Get Help

kvantakala August 30, 2019, 2:18am 3

@aercio.melo - any chance it’s linked to this: Unable to Authenticate on a specific WiFi Network

Topic		Replies	Views
Callback UnauthorizedError not deleting auth0 cookie for a domain Archived content rules , cookie	2	3918	December 24, 2018
HTTP Status code 431 header too long Get Help	5	8990	March 25, 2020
Auth0-nextjs - Logout failure due to race condition with Set-Cookie Get Help logout , sessions	2	2050	November 24, 2022
Delete Auth0 cookie on signout Archived content delete , cookie , lock-11 , auth-9	2	5214	December 14, 2018
V2/logout not clearing auth0 session cookies Get Help logout , auth0 , cookie	8	9951	April 1, 2025

Cookies not cleared on logout causing http 431 errors

Related topics