TomasV.49484 (Customer) asked a question.
Headers too large - Login Fails - Windows MVC
Hello,
I have a MVC app that works most of the time.
Every once in a while, the login process loops between Callback/Login/authorize.
When the flow returns to the callback, the user is sent to Login and the authorization process begins all over again.
Eventually the process fails with a "headers too large" error.
If I restart my application pool, the login process succeeds.
Comparing the Network Logs in Chrome, I can see that the initial call to /Callback is not setting the "OpenIdConnect.nonce.xxx" cookie nor the ".AspNet.Cookies" cookie
Why would the /callback endpoint not set these cookies?
Any insights are appreciated.
-tomas
Hi, @TomasV.49484 (Customer)
Thank you for posting on our Community page!
The HTTP Error 431: Request Header Fields Too Large response status code indicates that the origin server refuses to fulfill users' requests. This issue happens when HTTP headers are too large. When facing this error message, consider clearing the cookies, shortening the referrer URL, and optimizing code.
You can find more info here:
https://www.okta.com/identity-101/http-error-431/
My advice would be to also leverage the Okta Developer forums for this type of questions and take advantage of their expertise.
https://devforum.okta.com/
Thank you for reaching out to our Community and have a great day!
_____________________________________________________________________________
What you missed: new product releases and other announcements
_____________________________________________________________________________
Community members help others by clicking Like or Select as Best on responses. Try it today.
_____________________________________________________________________________