Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Bad request - Header Field too long" #1868

Open
realdadfish opened this issue Jul 31, 2023 · 1 comment
Open

"Bad request - Header Field too long" #1868

realdadfish opened this issue Jul 31, 2023 · 1 comment
Assignees
Labels
Inevstigation Engineering team as looked into the issue and needs deeper investigation to provide a conclusion
Projects

Comments

@realdadfish
Copy link

realdadfish commented Jul 31, 2023

Describe the bug
This issue pops up for some of our production users. After starting the authentication flow and selecting a user certificate, the MSAL library request results in an error 400 "Bad Request - Header Field too long"

Smartphone (please complete the following information):

  • Device: Nokia X20
  • Android Version: Android 13
  • Browser: Probably WebKit WebView
  • MSAL Version: 4.1.3

Stacktrace
n/a

We've figured other places where this issue pops up in Azure AD, though not on Android, like https://stackoverflow.com/questions/46100272/azure-portal-bad-request-request-too-long#:~:text=The%20error%20HTTP%20400%3A%20Size,O365%2C%20Azure%2C%20etc, however, we're unable to find a way influencing the library's cookie / authentication handling to follow any of the advice that is given.

@negoe negoe added this to Needs triage in Bug Triage Aug 7, 2023
@negoe negoe moved this from Needs triage to Committed in Bug Triage Aug 14, 2023
@negoe negoe assigned negoe and melissaahn and unassigned shahzaibj and negoe Aug 14, 2023
@negoe
Copy link
Contributor

negoe commented Aug 14, 2023

@realdadfish Can you please upgrade the library to latestversion and check if you still experiencing the issue?

@negoe negoe assigned negoe and unassigned melissaahn Aug 14, 2023
@negoe negoe moved this from Committed to Investigation Required in Bug Triage Aug 14, 2023
@negoe negoe moved this from Investigation Required to In Progress in Bug Triage Oct 4, 2023
@negoe negoe moved this from In Progress to Investigation Required in Bug Triage Oct 4, 2023
@negoe negoe added the Inevstigation Engineering team as looked into the issue and needs deeper investigation to provide a conclusion label Oct 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Inevstigation Engineering team as looked into the issue and needs deeper investigation to provide a conclusion
Projects
Bug Triage
  
Investigation Required
Development

No branches or pull requests

4 participants