title: Google oauth2 and 400 bad request: Bug on Google side?
body: <p>We have Google oauth2 working fine on our website. However, often Chrome users complaint about 400 Bad request and we were able to reproduce it now. Based on the investigation, it indeed looks like a bug on Google side:</p>
  
  <ol>
  <li>It only happens with users who were authenticated earlier and logged-in with multiple accounts on GMail</li>
  <li>It doesn't happen when the same user uses incognito window.</li>
  <li>This problem is universal and not only with our website. At this moment, I am not able to login using google oauth2 on any website including StackOverflow. Stackoverflow site also gives the same 400 Bad request error and I have to use incognito. </li>
  <li>No additional information is present along with 400 Bad Request Error</li>
  <li>To further confirm, I just loaded <a href="https://accounts.google.com/o/oauth2/auth" rel="noreferrer">https://accounts.google.com/o/oauth2/auth</a> without any parameters and it also gave 400 Bad request. However, if I load it in incognito, it gives Error: invalid_request. So there is indeed different behavior. </li>
  <li>So We suspected that the problem might be with cookies sent along with request since incognito window has no cookies. So we cleared all the cookies for domain accounts.google.com and problem magically solved. This confirms that Google side of code is not able to handle their own cookies. </li>
  </ol>
  
  <p>We really need to solve this. Please help. Do let me know if you need any information.</p>