When browser cookies go bad: How to avoid ‘bad header’ problems on favorite websites - wilsonobblet

Host errors for websites you frequently visit are a pain. Most of the time these are impermanent problems that the sites in question fix on their end after a few minutes. But there is one problem that does pauperization your attention

The horrific "Bad Request" error.

Have you ever been refused service at a website you frequent with an error message that says, "400 Bad Request. Request Header OR Biscuit To a fault Large?"

It's an annoying job typically caused by the Nginx web server, and it typically happens for one of two reasons. Sometimes the website using that software doesn't allow browser cookies over a certain size, or cookies stored in your browser might be corrupted. The easiest way to solve this problem is by deleting the cookies for that internet site.

The quick and fecal way is to delete all the cookies in your cache, but that would poor losing saved data for other sites—including logins. That's a big hassle if you ask me.

Instead we're going happening a targeted delete mission to abolish the sinning cookies. Here's how to act that in Google Chrome, Mozilla Firefox, Internet Explorer, and Microsoft Edge.

Chromium-plate

Deleting cookies in Chrome.

Overt a new lozenge and so type the following into your turn to bar: chrome://settings/cookies and hit Enter.

A small window will appear known as Cookies and site information. Eccentric the name of the website you ask to target area into the search prevention in that window. In my instance IT's "blogs.microsoft.com."

Once the sinning site appears in the main division of the window, spotlight it, and then press the red 'x' on the far right. Right away try out going to the difficult site again.

If that ease doesn't work, conk back to the cookies tablet and delete any entries for the parent site (in this case it's microsoft.com). Now go back to the offending website one last time and everything should be working ticket.

Firefox

Firefox's cookies window.

To delete specific cookies on Firefox, type about:preferences#privacy into the address bar and hit Enter. Now from the privacy tab that opens click the Demonstrate Cookies… push button.

Quasi to Chrome, search for the website cookies you want to erase in the text entering bar at the top of the small windowpane entitled Cookies. Select the ones you need to edit and click Remove Elect.

Go back and test your site, and everything should be running satisfactory. If not, follow the final steps mentioned above in the Chrome surgical incision.

Internet Explorer

Click the Settings cog in the upper berth proper corner of the web browser window and select Internet options from the drop-consume menu. In the small windowpane that opens go to Broad > Browse Story > Settings > View files.

This little trick leave open a File Adventurer windowpane at the location where IE saves its cookies. Now search the brochure you just opened in File Explorer for the site in question. Then delete the cookies you need to abolish just like you would any other file: Click and drag the files into the Reuse Bin, or right-click the files and pick out Delete.

Microsoft Bound

Deleting cookies in Sharpness is currently all or nothing.

Microsoft's newest browser doesn't have the same granular options that the otherwise browser practice—at to the lowest degree that I could discovery. Therein character, you'll have to delete all your cookies and saved site data to sire obviate the problem.

To do this, click happening the three horizontal dots in the upper precise-hand corner. Next get across Choose what to free under the Clear browse information gallery. Uncheck everything but the choice for Cookies and salvageable website data. At once flick Trenchant, and you're done. If that lul doesn't help, proceed back and clear the Cached information and files choice as well.

Source: https://www.pcworld.com/article/415490/when-browser-cookies-go-bad-how-to-avoid-bad-header-problems-on-favorite-websites.html

Posted by: wilsonobblet.blogspot.com

Share this post