Bad Request Error 400 Gmail Safari
Contents |
the "400 Bad Request" error message from a website Posted on October 24, 2012 by Timour Rashed Problem: Whenever you bad request error 400 gmail chrome access any website from a specific domain. For example http://www.abc.com/morepages/…. In
Bad Request Error 400 Gmail Firefox
the URL above, the domain is "abc.com" and "morepages" is a sub-site. The problem shows as the following: bad request error 400 google apps Bad Request Your browser sent a request that this server could not understand. Size of a request header field exceeds server limit. Cookie ----------------- Solution: It wasn't clear at
Bad Request Error 400 Adwords
first but the error message is telling me exactly what the problem is (the keyword here ladies and gentlemen is "cookie") The problem was due to a cookie that has become corrupted. Not sure how it got that way but it seems that the last time it was generated something went wrong. The easy solution is to delete error 400 bad request fitbit all your cookies but here is the best way to solve that specific issue, I have created a customized guide for Firefox, Chrome, and Internet Explorer. Firefox 1. Access the options from the main menu 2. Go to the Privacy tab 3. Click "remove individual cookies" 4. You will get the window below and you can search for cookies on that specific domain (in our example abc.com) 5. To delete the cookies, just select and click "Remove Cookie" 6. Try accessing the site again, if you still have issues you can repeat from step 4 Internet Explorer 1. Access the options from the main menu Tools -> Internet Options 2. Select Settings under the "Browsing history" section in the General tab 3. Select "View files" 4. You can search for those cookies and manually delete them Google Chrome 1. Click on Settings 2. Enter "cookies" in the search field then click "Content settings" 3. Click "All cookies and site data" under Cookies 4. Select the specific cookie to delete the cookie -------------
from GoogleSign inHidden fieldsSearch for groups or messages
Gmail using Chrome, chances are that you might have encountered the dreaded Bad Request Error 400 error. The error is so frustrating and vague that most users are left clueless on how to http://techathlon.com/fix-bad-request-error-400-gmail-google-chrome/ fix it. Most importantly, many of us do not have the time to fix the issue when we have to send that all important email. There are a number of forum posts on the Internet in which users mentioned that they have moved to Firefox or other browsers just because of this problem. Its a shame that both the browser and the email are from the provider bad request and they are yet to fix it even though users have had issue for about an year! But thankfully many users have improvised and found work around to this issue. The problem appears to be with the GMAIL_IMP value stored in the cookie for mail.google.com. No one seems to have an idea what is actually causing the error. Here I have picked 3 fixes and classified them bad request error as the Good, the Bad and the Ugly depending on the complexity of the fix. Lets start with the Ugly… The Ugly Right click on the screen. Select Inspect element. Select the Resources tab at the top of the Developer Tools window. Expand the Cookies section in the left side navigation by clicking on the arrow next to Cookies. Select the mail.google.com cookie. Right click on GMAIL_IMP. Select Delete. Close the Developer Tools window. Refresh the page giving you the error. The Bad (Warning: you will be signed out of all your Google account) Get to Chrome Setting. Click Show advanced settings. In the Privacy section, click the Content settings button. In the "Cookies" section, click All cookies and site data to open the Cookies and Other Data dialogs. In the search box search for mail.google.com. Click Done Refresh the page giving you the error. The Good Just navigate to any of this URLs Labs turned on mail.google.com/mail/?labs=1 Labs turned off mail.google.com/mail/?labs=0 This fix is the easiest, but make sure you do this all the time as it will not address the cookie issue. Better still would be convert your default gmail interface to Gmail Offline. You can read on how to do this here http://techathlon.com/a-better-and-ad-free-gmail-interface/ Goog