Often when you visit a
How to Solve Cookie Too Big or 400 Bad Request Header ChromeHere is a quick guide to clear the error request header or cookie too large or too big chrome, IE, Mozilla FireFox and Edge browser and proceed with surfing Internet.
Request Header or Cookie Too Large or cookie too big error will not let you surf Internet due to large number of corrupted cookies or if the headers are really big, nginx will be rejecting it. The default buffer number is 4 and size 8k. If the headers are bigger than 8k, nginx will reject them.
Kindly follow the below steps to solve 400 Bad Request Header or Cookie Too Big or Cookie too Large in Chrome.
|Googling cookie too big???|
400 Bad Request usually happens when the server finds the cookie for that domain is too big to load or corrupted.Usually
What is 400 bad request request header or cookie too large error?
How to Avoid 400 Bad Request, Cookie Too Large - Chrome, IE, Firefox, Edge ErrorStep 1: Check the URL typed in the browser whether the syntax is correct or not. The URL of the website such as https://www.shipmethis.com or http://www.shipmethis.com should be proper. If it is http:/www.shipmethis.com the web page wont load and provide an error. Recheck the website address.
Hard Refresh The BrowserStep 2: If the webpage address is proper, then do Refresh the
Use Incognito Mode or Private ModeStep 3: To check if it the problem with corrupted cookies, Use incognito or Private mode in the browser. Go to Settings and activate in-cognito browser window. This will not store cookies and if the website loads, then it is the problem with corrupted cookies. In that case delete the cookies.
You need to delete the cookie stored in your browser. Go to settings and clear cookies and cache. Restart the browser. You may have to delete the cookies again after you restarted the browser.
Press CTRL+SHIFT+N to open in cognito mode in Google Chrome. Try to access the website there.
For 400 bad request nginx chrome Chrome Users;Step 1: Type "chrome
OR Go to Settings from the sidebar
|400 Bad Request, Cookie Too Big - Chrome|
Step 3: Select "Clear Browsing Data"
Step 4: Select "Cookies and other site and plugin data"
Step 5: Press "Clear Browsing Data"
For request header or cookie too large Mozilla FireFox Users
For request header or cookie too large wordpress Internet Explorer [IE
For request header or cookie too large Edge Browser Users
Step 4: If the website is not loading in the in-cognito browser and still having the Cookie Too Big or 400 Bad Request Header error, then you need flush DNS of your computer.
Step 5: Flush DNS : Press Windows Button+ R to get run window [command prompt in Microsoft Windows]. Type "cmd" without quotes and enter. Check other Ways to open Command prompt.
Type ipconfig /flushdns and press enter.
Then go to the browser and see if the website is loading. If not restart the DNS service.
DSN Client Service in WindowsStep 6: Restart DNS Client Service : Right click on task bar and select Task manager. Or go to start menu and type task manager to open it. Select Services. Find DNS client from list of services. Restart the service. Once the service is restarted, open the browser and try to load the website again. If it not loading, then you can have to use TDSS tool to identify malware in the system.
Step 7: Run TDSS Killer Tool from Kaspersky: IDSS detects any root kits on your computer and remove them. A rootkit is a program or a program kit that hides the presence of malware in the system. You can download it from here: http://support.kaspersky.com/viruses/utility#TDSSKiller
Step 8: If it does not work, you can try proxy servers. This will mask your IP address and open the website. I have explained the use of proxy websites in the video. Any issue because of servers and ip address will get resolved by this method.
Share the post if the error 400 Bad Request Header or Cookie Too Large in Chrome, IE, Edge, Firefox is solved.
Kindly spend 5 seconds to share this post