usefulbulk logo

How to Restore Functionality of Your Chrome Browser After Encountering a "Bad Request-Request Too Long" Error on a SharePoint Server

THE PROBLEM

If you've been working on a SharePoint server with Google's Chrome browser (and probably browsers as well) and subsequently encounter the error message:

Bad Request-Request Too Long

HTTP Error 400. The size of the request headers is too long.

. . . the problem is probably because the server has issued your browser too many "cookies."

THE SOLUTION

In Chrome, the solution to restoring access to the SharePoint site is relatively easy to execute. Here are instructions for removing only SharePoint cookies, based upon Google's instructions to Manage your cookies and site data:

  1. Save your work.
  2. Close any browser windows/tabs associated with the SharePoint site. (At the end of this process, you may have to log in to the SharePoint site again.)
  3. Click the Chrome menu on the browser toolbar. Select Settings.
  4. Click Show advanced settings at the bottom of the page.
  5. In the "Privacy" section, click the Content settings button.
  6. In the "Cookies" section, click All cookies and site data to open the Cookies and Other Data dialog.
  7. To delete all "SharePoint" cookies, type "sharepoint" in the "Search cookies" field in the upper-right corner of the dialog. One or more lines of matching items with domain names containing "sharepoint" will appear.
  8. Hover your cursor the line with the domain name of the site with which you are getting "Bad Request" messages. An "X" will appear to the right end of the item line.
  9. Clicking on the "X" will delete all the cookies associated with that site.

This should allow you to again use the Chrome browser for accessing the SharePoint server.

home