Request Header or Cookie Too Large: What It Is + Easy Fixes

PDF download Download Article
Understand bad request header error on Chrome or other browser
PDF download Download Article

Are you getting the "Request Header Or Cookie Too Large" error code? You may also see "400 Bad Request" when trying to visit a website. This is a common error, and luckily, it can be fixed by checking a few things on your device. Here's what Request Header Or Cookie Too Large means and how to fix it on Google Chrome, Safari, and more browsers.

Quick Fixes

  1. Clear your browser's cookies and cache.
  2. Reset your browser's settings.
  3. Reduce your file size.
  4. Restart your device.
  5. Flush your DNS cache.
  6. Contact the site owner.
Section 1 of 3:

What does Request Header or Cookie Too Large mean?

PDF download Download Article
  1. The 400 Bad Request error may pop up when you try to load a website and your request gets denied by the server. When you try to visit a website, your browser sends data to the website's server. When the size of the data is too large for the server, you'll usually see this error. [1]
    • This error can happen due to your own device or the website itself.
    2. Advertisement
Section 2 of 3:

Common Causes

PDF download Download Article
  1. When you visit a website, files called cookies are created as it saves your browsing data. The cache remembers other parts of the website, such as images. Leaving your cookies and cache alone when you browse the internet can make your frequently visited sites load faster. However, these files can become corrupted over time and cause errors when trying to access the website again.
  2. If you're trying to upload a file onto a website, you may be trying to upload a file that is too large for the server to handle.
  3. Similar to other files, your browser can become corrupted. Whether it breaks from a past update or an outside source, you may have trouble visiting websites until the browser itself gets fixed.
  4. The DNS cache stores records of the domains you have visited. Similar to cookies and cache on your browser, you can clear the DNS cache on your device if the files have become corrupted.
  5. Some site owners may block traffic to their website if it's currently undergoing construction or if they no longer wish to maintain it. In this case, it's entirely up to the site owner if they want to get it back up and running. [2]
    6. Advertisement
Section 3 of 3:

Troubleshooting

PDF download Download Article
  1. Clear your cookies and cache . This process will vary depending on your device. [3]
    • If you're using a desktop or mobile browser:
      • Locate the History menu.
      • Select the option that says something like “ Clear browsing history ” or “ Clear Recent History ”.
      • Make sure Cache and cookies or similar options are selected.
      • Set the time range to All , Everything , or similar.
      • Select Clear history .
    • If you're using Safari on iOS:
      • Navigate to Settings > Apps .
      • Select Safari .
      • Tap Clear History and Website Data .
      • Select a timeframe and tap Clear History .
  2. Most browsers have an option in their settings menu to restore the browser’s default settings.
    • For example, if you're using Google Chrome, do the following:
      • Click ⋮ .
      • Click Settings .
      • Click Reset settings .
      • Click Restore settings to their original defaults .
    • If you don't have this option, uninstall your browser, and then download it again.
  3. If you're trying to upload a large file, try compressing it into a ZIP file before you upload it. This will reduce the size substantially. Alternatively, try a different sharing method, such as Google Drive .
  4. Sometimes, a quick restart can fix common issues. Turn off your device fully, wait at least 30 seconds, and then turn it on again.
  5. Make sure your internet connection is strong and stable. If you're using cellular data, you may not have a strong enough connection.
  6. Flushing your DNS cache can ensure you have the newest information for the website. This will remove any old and corrupted data.
    • If you're using Windows:
      • Open the Start menu and type "command prompt".
      • Right-click Command Prompt and select Run as administrator .
      • Click Yes to confirm.
      • Type ipconfig /flushdns and press Enter .
    • If you're using Mac:
      • Open the Terminal .
      • Type sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder and press Enter/Return .
  7. In some cases, you may not be at fault. If the site isn't equipped to handle the traffic or if there's something wrong on their end, you won't be able to successfully load the website. If they aren't available via email or phone, you may be able to find the owner on social media.
    8. Advertisement

Expert Q&A

Ask a Question
200 characters left
Include your email address to get a message when this question is answered.
Submit
      Advertisement

      Tips

      Submit a Tip
      All tip submissions are carefully reviewed before being published
      Name
      Please provide your name and last initial
      Submit
      Thanks for submitting a tip for review!

      You Might Also Like

      How to
      Clear Your Web Browser Cache on Any Platform
      Clear Your Web Browser Cache and Cookies on Any Platform
      How to
      Download Any Video for Free: 5 Step-by-Step Methods
      How to
      Allow Pop–ups
      How to
      Enable Cookies in Your Internet Web Browser
      8 Easy Ways to Fix reCAPTCHA Not Working in All Browsers
      How to
      Block Cookies in Chrome, Safari, & More
      How to
      Change Your Country in Tor on Windows, Mac, & Linux
      How to
      Uninstall Microsoft Edge Permanently from Windows 10 or 11
      3 Simple Ways to Make the Taskbar Transparent in Windows 10/11
      How To Refresh a Webpage: Desktop & Mobile
      How to
      Set Google as Your Default Search Engine: 11 Easy Ways
      How to
      Get Around Parental Controls on the Internet
      How to
      Bookmark a Website in Any Browser
      Advertisement

      References

      1. ↑ https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/troubleshoot-dotnet-sdk-request-header-too-large
      2. ↑ https://www.geeksforgeeks.org/how-to-fix-400-bad-request-request-header-or-cookie-too-large/
      3. ↑ https://www.geeksforgeeks.org/how-to-fix-400-bad-request-request-header-or-cookie-too-large/

      About This Article

      Thanks to all authors for creating a page that has been read 303 times.

      Is this article up to date?

      Advertisement