![After succesful login with access control, 400 error: Request Header Or Cookie Too Large - Access - Cloudflare Community After succesful login with access control, 400 error: Request Header Or Cookie Too Large - Access - Cloudflare Community](https://global.discourse-cdn.com/cloudflare/optimized/3X/e/a/eab7e43f771c4aa9b4fbcc39c1095b531af47e4c_2_488x500.png)
After succesful login with access control, 400 error: Request Header Or Cookie Too Large - Access - Cloudflare Community
![Damian Gryski on Twitter: "Anyone getting 400 Bad Request (Request Header or Cookie Too Large) from @GitHubEng? Weird cookies in Chrome: https://t.co/UEvmIfd9TV" / Twitter Damian Gryski on Twitter: "Anyone getting 400 Bad Request (Request Header or Cookie Too Large) from @GitHubEng? Weird cookies in Chrome: https://t.co/UEvmIfd9TV" / Twitter](https://pbs.twimg.com/media/Cfg8EnBWcAAm5Ej.png:large)
Damian Gryski on Twitter: "Anyone getting 400 Bad Request (Request Header or Cookie Too Large) from @GitHubEng? Weird cookies in Chrome: https://t.co/UEvmIfd9TV" / Twitter
![400 Bad Request - Request Header or Cookie too large - on public meet.jit.si instance · Issue #8380 · jitsi/jitsi-meet · GitHub 400 Bad Request - Request Header or Cookie too large - on public meet.jit.si instance · Issue #8380 · jitsi/jitsi-meet · GitHub](https://user-images.githubusercontent.com/5689/104216118-438cd100-53ff-11eb-99d4-0ecf0f6f6814.png)