Forum Discussion
Portal giving Bad Request error again
Can you guys please fix this once and for all? The issue appears every few months, is it that hard to remember to check for cookie lenght? 🙂
This time it seems to be the s.LoginContext one, as well as the s.BECContext. RPSSecAuth is quite large as well.
Can't remember who was responsible for this, so lets try Anne Michels 🙂
Hi Vasil,
we're actively working on that. Please keep the feedback coming!
thanks,
Anne
- I sometimes get redirect to https://www.office.com/landing with a generic browser site not available error. After a page refresh everything works fine again.
I used to experience that error a lot, and had to configure Chrome to clear cookes for a couple of O365/MSOnline URLs at close so that the problem wouldn't keep occuring (would happen for OWA, Portal, here on the Tech Community as well). Of course that also meant constantly logging back into things. For the last month or two I've had the cookie removal rules disabled and it's been fine for me.
That's what I'm trying to avoid though, all those nasty MFA logins :) And it's about time they learn to properly code those cookies!
And here's another example on the same issue from Answers: https://answers.microsoft.com/en-us/msoffice/forum/msoffice_o365admin-mso_manage/admin-panel-issue-bad-request-request-too-long/e54d42e2-ce3b-4647-9793-1c037cccc9b0
And an example of how aggravated I'm getting with it :)
- Anne Michels
Microsoft
Hi Vasil,
thanks for flagging. Could you please submit this through the feedback button in the admin center on the page this happened? That way, the engineering team can more easily connect this with the right logs and investigate.
Thanks,
Anne
- Aaaaaaaaaaaaaand yet another one, MicrosoftApplicationsTelemetryDeviceId. Getting tired of this...
I see this kind of thing in Chrome more than IE. But it's a pain in the ass and the engineering team needs to get a handle on why so many cookies are used and how these cookies cause things to break.
- At last - been struggling with this for over a year. As a partner, I often get issues by logging in with a tenant id and being prompted (or worse, automatically logged into)a different tenants information. Incredibly inconvenient and a huge security issue that Microsoft seem to think is not their problem in my previous dealings with them.
I found that creating a chrome user profile for each tenant and launching chrome in that user profile fixes the wrong tenant problems and I don't get cookie issues.
Ideally I wanted a script that would just nuke the relevant cookies in chrome, but I was not able to work out how to do this from the command line. Doing it in the gui is several clicks and time consuming when I have to do it 15-20 times a day. - Anne Michels
Thanks for flagging again, Vasil. I've shared your feedback with our engineering team and they are looking into it.
Thanks,
Anne
Um? Anne Michels that's an old thread, this issue hasnt happened recently and I believe it to be fixed now :)
We did have a short outage in parts of EMEA earlier today, but I cried about that in another thread.
- Anne Michels
How wierd! This landed in my inbox today. But good if it's been resolved!
+1 still a problem with viewing profiles on delve. This affects everyone in our org at different times. Not a great experience. We're building something that we sell to our customers and it doesnt look good on us that making apps that work with your APIs only work some of the time and is out of our control..
