Home > Chrome, Gmail, Google, Web > Resolving ‘Bad Request Error 400′ in Gmail on Chrome

Resolving ‘Bad Request Error 400′ in Gmail on Chrome

Gmail on Chrome: Bad Request Error 400

Gmail on Chrome: How to resolve the Bad Request Error 400

I periodically come across the “Bad Request Error 400″ problem when using Gmail on Google Chrome. I’m not the only one as you can see from a Google search on the topic. One minute all is well and the next, reload after reload all you see is a blank page and this error message. You haven’t changed anything but things just don’t work anymore. If you try accessing Gmail on a different browser like Firefox, everything seems good, so it’s not Gmail itself; it’s the combination of Gmail and Chrome.

It seems quite ridiculous really that this issue should happen on Chrome. Shouldn’t Gmail on Chrome be essentially bulletproof? Google on Google. C’mon.

When looking for answers the most common suggestion you’ll find is to clear all of your browsing data; history, cache, cookies, etc. I happen to like my browsing data. Among other things, it helps me find things and allows me to stay logged in on various sites. Deleting it all causes me pain.

After searching through various sites and the Gmail and Chrome forums I finally found a great solution. It turns out deleting all of your browsing data is not necessary. This problem comes down to one solitary cookie. Delete this cookie and life is good again.

How to resolve the Bad Request Error 400 in Gmail

Here are the exact instructions.

– Right click on the page with the error
– Select “Inspect Element” from the right click menu
– Select the “Resources” tab at the top of the Developer Tools pane or window that opens up
– Expand the “Cookies” section on the left side navigation by clicking on the little triangle next to “Cookies”
– Select the “mail.google.com” cookie
– Right click on “GMAIL_IMP”
– Select “Delete”
– Refresh the error page

– Rejoice

Original source of solution

 

 

 

Categories: Chrome, Gmail, Google, Web Tags: , ,
  1. No comments yet.
  1. No trackbacks yet.