Bugfix: Chrome login fails with 400 request headers too long #525#717
Open
ShwetaKumari-programming wants to merge 3 commits intoMrSwitch:mainfrom
Open
Bugfix: Chrome login fails with 400 request headers too long #525#717ShwetaKumari-programming wants to merge 3 commits intoMrSwitch:mainfrom
ShwetaKumari-programming wants to merge 3 commits intoMrSwitch:mainfrom
Conversation
…ader size errors in Chrome
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Some users were experiencing a HTTP 400 – “The size of the request headers is too long” error when calling hello.login() in Chrome. The issue did not occur in Incognito mode or in other browsers, and Azure B2C itself was functioning correctly.
This behavior was caused by excessive data being included in request headers, which can accumulate over time in Chrome due to stored session data, cookies, or repeated authentication attempts. When Chrome’s header size limit was exceeded, the login request failed before reaching Azure B2C.
This PR fixes the issue by adjusting the login flow to prevent oversized request headers, ensuring consistent behavior across Chrome, Incognito mode, and other browsers.
What’s Changed
Fixed hello.login() failing in Chrome due to oversized request headers
Reduced/cleaned unnecessary data sent during authentication requests
Ensured login works consistently across browsers, including Chrome