How to fix 400 Bad ...
 
Share:
Notifications
Clear all

How to fix 400 Bad Request errors (and other 4xx errors)

Wendell
(@wendell)
5,000+ posts Admin

When you get a "400 Bad Request" error in your browser (or similar error in the 400 series) while viewing some pages on our website, you may have some corrupted cookies stored on your computer. If you don't want to delete all cookies on your computer, which would wipe out all your "remember me" sites, you'll want to delete only the cookies associated with rplstoday.com. Here's how (in Chrome and Firefox):  https://www.thewindowsclub.com/clear-cache-cookies-specific-website

 

Quote
Topic starter Posted : November 26, 2018 9:28 am
Brad Ott liked
Brad Ott
(@brad-ott)
5,000+ posts Supporter

Just did this for my Chrome.  Thanks W.

ReplyQuote
Posted : November 26, 2018 10:57 am
Wendell liked
Glenn Borkenhagen
(@glenn-borkenhagen)
200+ posts Member

The Firefox instructions provided at Wendell's link are apparently for an earlier version of Firefox.

Here are instructions from the Firefox support system -

Delete cookies for a single site

To delete cookies for one website:

  1. Click the menu button Fx57Menu and choose Options.
  2. Select the Privacy & Security panel and go to the Cookies and Site Data section.
    Fx63settings-AcceptCookies
  3. Click the Manage Data… button. The Manage Cookies and Site Data dialog will appear.
  4. In the Search websites field, type the name of the site whose cookies you want to remove. Items that match your search will be displayed.
    Fx60ManageCookiesAndSiteData-RemoveSelected
    • To remove all cookies and storage data for the website, click Remove All Shown.
    • To remove selected items, select an entry and click Remove Selected.
  5. Click Save Changes.
  6. In the Removing Cookies and Site Data confirmation dialog that opens, click OK.
  7. Close the about:preferences page.

To learn more about managing site data in Firefox, see Manage local site storage settings.

Note: You can use the Storage Inspector to remove individual cookies for a specific website, via the right-click context menu. To open the Storage Inspector, go to the menu button Fx57Menu Web Developer submenu or press Shift + F9 on the keyboard.
ReplyQuote
Posted : November 26, 2018 3:54 pm
dms330 and Wendell liked

Wendell
(@wendell)
5,000+ posts Admin

Thank you, @glenn-borkenhagen, for the follow-up!

ReplyQuote
Topic starter Posted : November 26, 2018 5:14 pm
markaldo
(@markaldo)
FNG Member

The 400 (Bad Request) status code indicates that the server cannot or will not process the request because the received syntax is invalid, nonsensical, or exceeds some limitation on what the server is willing to process. It means that the request itself has somehow incorrect or corrupted and the server couldn't understand it. The server is refusing to service the request because the entity of the request is in a format not supported by the requested resource for the requested method. Therefore, it prevents the website from being properly displayed. The main thing to understand is that the 400 Bad Request error is a client-side error.

The cause of a 400 error can be a wrongly written URL or a URL that contains unrecognizable characters. Another cause of the error might be an invalid or expired cookie. Also, if you try to upload a file that's too large. If the server is programmed with a file size limit, then you might encounter a 400 error.

 

ReplyQuote
Posted : February 28, 2022 9:28 pm
Share: