Clearing browsing data, cookies and cache images

Question

Hi All:

My Optonline email server crashes and displays a '400 Bad Request, Request Header Or cookie Too Large' message which I know means I need to clear the browsing data, cookies and cache, however, I have not been able to find the pull downs through the 'Privacy and Security' settings in Google Chrome.

How can I resolve this issue?

Thank you.

Answer 1

Hi Luis,

Thank you for sharing your question. Sorry to hear you're getting that 400 Bad Request error with your Optonline email – super annoying, I know. It usually pops up when your browser has too many cookies or old data hanging around for that site. Clearing them out usually does the trick. I am here to help.

Here's what you can do:

Open Chrome, hit those three dots in the top right, and click on Settings.

Head over to Privacy and Security, then Clear browsing data.

In the window that pops up, check the boxes for Cookies and other site data and Cached images and files.

Set the time range to All time to really clean things out, and then click Clear data.

Restart Chrome, and try your Optonline email again.

If you just want to clear things for Optonline, go to Privacy and Security > Site settings > View permissions and data stored across sites, find Optonline, and remove its cookies.

 

I hope this helps.

 

Best Regards,

Noel

Answer 2

To resolve the "400 Bad Request, Request Header Or cookie Too Large" error in Google Chrome, you need to clear your browsing data, including cookies and cached images. Here’s how you can do that:

1. Open Google Chrome.
2. Click on the three dots in the upper right corner to open the menu.
3. Select Settings.
4. In the left sidebar, click on Privacy and security.
5. Click on Clear browsing data.
6. In the dialog that appears, select the time range (e.g., Last hour, Last 24 hours, All time).
7. Check the boxes for Cookies and other site data and Cached images and files.
8. Click on Clear data.

This should help in resolving the issue by clearing the excessive cookies and cache that are causing the request header to be too large.