Fixing the “Bad Request – Request Too Long” Error with Office 365 in Chrome

Bad Request - Request Too Long

This one really bugs me when it happens, and it’s pretty frequent. If you try to navigate to your Office 365 Settings or the Admin Portal in Office 365 with Chrome, you may well get this error instead of arriving at your regularly scheduled destination. I believe you may have a similar experience in Firefox as well.

I’ve gone Bingling for clues more than once on this one and I find lots of complaints about it happening, but the only solution seems to be “delete your cookies”. This is not an acceptable answer by any stretch of my imagination, but apparently it actually does work.

Eagle-eyed Twitter follower Harold Gale (@1wisegeek – aptly named!) spotted my compaint about it today and came to the rescue with a post with a very targeted fix.

In the hopes that it will help a few more people (and maybe rise a little higher on the Bingling charts so that they can find it!), here are the steps to the solution, temporary as it may be.

  • Go to the the Chrome Settings – usually this will be under the three vertical dots (sideways elipsis? leaky |?) in the top right of your window.

  • At the bottom of the page, click “Show advanced settings…”
  • Under Privacy, click the “Content Settings” button
  • Click on the “All cookies and site data…” button

  • In the search box in the upper right, search for “login.microsoft”

 

I found all these cookies after that search. Note the *5* “testcookie” entries. Enterprise-class!

You can also search for “office365” and/or “office.com” and delete some of those cookies as well.

Note that I have no idea what each of those cookies does, and you will want to be thoughtful about what you delete!

My hope is that this post gets few reads because Microsoft solves the issues here, but the Office 365 login “experience” has been less than stellar for many years now. I’m not going to hold my breath, and at least I know I have this post to help future me out more easily.

Similar Posts

15 Comments

  1. Try the cookie for site office.com called ‘RPSClearCT’. I did it by process of elimination one at a time and after that cookie being deleted the error went away.

  2. Thanks for pointing out the problem.
    I found out the easier way is to click on the (i) icon before the url (view site information) -> Cookies (x in use) and delete all of them.

  3. I was having this issue as well. My site was loading fine until today. Hopefully Microsoft fixes the issue for good.

  4. I was having issues with protection.office.com – when i looked at the cookies there were about 25 cookies with what looked like long data strings in the content, i deleted them and that fixed the issue for me.

  5. Thank you all so much. This worked for me, from above: click the lock icon (left of URL textbox) on chrome to see the “cookies in use” and delete every single one. I had 55+. Closed all browsers and went to office.com and logged in, went to admin and worked perfectly.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.