Forum Discussion
Chrome "400 Request Too Long" when navigating to profile
Last week I started noticing that in Chrome our people search web parts were intermittently not showing user's profile pictures, and that clicking on the link to their Delve profile would result in a "400 Request Too Long" error. Also, trying to get to your own profile via the top-right "About me" link would also result in a 400 error. Anyone else experiencing this? It's breaking our directory web part as well as links to profiles.
Edit: It was just happening again, and I found out that I can't get to any part of Delve, either from the App Launcher or from the Portal. Same 400 error, only occuring in Chrome, and it seems to go away on its own after a few minutes.
Edit 2: The problem is also occuring in Edge. Internet Explorer is the only browser that does not seem to be having this issue.
Here's the error message I receive when using Chrome:
Our directory CSWP isn't loading any profile pictures:
Clicking "About me" results in the same 400 error:
Same issue here :(
Hi All, this has been plaguing us for years at least three, however, when I went deep into it the issue seemed to stem from IIS and a setting for maximum path in cookies, basically it could be addressed but won't and deleting cookies will be the only way until it causes enough pain to enough people that someone truly does try and sort it out. Turn it off and on, restart PC, reinstall browser, delete cookies, reinstall the operating system. Rather than perform root cause analysis and fix it. ho hum
I' just solved my problem with the following hint:
So if I construct the URL like follows it works
<img class="ms-Persona-image" src="https://tenant.sharepoint.com/sites/SiteCollectionName/_layouts/15/userphoto.aspx?accountname='+person.SipAddress+'&size=M&url="' + person.PictureURL + '">'
from :https://github.com/giuleon/OfficeUIFabricPeoplePickerAddIn/issues/1#issuecomment-333039482
- Hello,
I have this issue with a similar development. It's happening in Firefox and Edge. In Chrome works well. Do you know how can this issue be fixed? Did you find a solution or a workaround?FWIW one year later people in my org still have this issue
- 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).
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.
Ha and of course I just encoutered 400 Bad Request in Edge for the first time while on the phone with O365 support... :-)
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).I'm seeing this in Edge, too, though, so it can't just be an issue with Chrome. I suppose this is another 'sit and wait' issue, since this isn't a viable solution at scale (almost everyone in my org is using either Chrome or Edge).
- Long discussion about "bad cookies" here: https://techcommunity.microsoft.com/t5/Admin-Center/Bad-cookies-and-the-Office-365-Admin-Center-and-the-Compliance/m-p/35095#M340
- Anne Michels
Microsoft
Adding Tom Batcheler
