Forum Discussion
Chrome "400 Request Too Long" when navigating to profile
Trevor Seward wrote:
You need to delete cookies for the related domains (related to *.live, *.microsoft, *.sharepoint). Chrome isn't handling cookie storage well and this has long been a problem -- it is not SPO-specific (e.g. happens with Microsoft Accounts on MSDN/TN forums).
This doesn't seem to be working for me, actually. Settings > Clear Browsing Data > Obliterate the following items from "the begging of time" > Check "Cookies and other Site Settings" > OK > close Chrome, reopen, same 400 error.
I also used an incognito window, which shouldn't have any cookies at all, and still got a 400 error.
- Jan 03, 2017
Ha and of course I just encoutered 400 Bad Request in Edge for the first time while on the phone with O365 support... :-)
- Tom BatchelerJan 23, 2017Former Employee
Hi Trevor Seward and Stephan Swinford,
We've been trying to repro this issue and can't nail it down. Can you reach out to me at tomb@microsoft.com if you're still having issues as we'd like to collect a couple more details from you.
Thanks so much
Tom
- Jim BarntishSep 11, 2017Copper Contributor
I am seeing this issue in my client's tenant. Same "HTTP 400 Bad Request: The size of the request headers is too long" messages when displaying profile images generated from a search web part. Additionally getting the same error when clicking My Profle.
For my client and myself, this is occurring in FF and Chrome. Fully resetting cache doesn't seem to change anything, nor does browsing in a private window.
Have there been any updates on this? Tom Batcheler, is there any additional information I can provide that would help diagnose this problem?