Smart Home & Tech
HTTP 400 Bad Request: What It Means and How to Fix It
Clean the address, then try one private window. Clear cookies for that site only if the private window worked. Do not edit headers.
Quick meaning
The server could not understand the request because it was malformed or invalid.
| Error | HTTP 400 |
|---|---|
| Family | HTTP |
Safe first actions
- Check the URL for typos or encoding errors
- Clear browser cache and cookies for the site
- Open the page in a private/incognito window
- Disable browser extensions one by one
- Reduce request payload size if uploading data
- Test on a different network or device
- Update browser and operating system
What not to do
- Repeatedly refresh without changes
- Assume the site is down
- Manually edit request headers in dev tools unless experienced
- Ignore browser console error details
When the website or provider must fix it
If the error persists after all client-side steps, the website or service provider must fix server configuration (e.g., header size limits, WAF rules, API parsing) or application code. Contact their support with the exact URL, steps tried, and any console error IDs.
HTTP 400 means the server received your request and refused it as a client error. The address, the form, or something the browser attached was not a request that server would process. A server or gateway answered this request. The response does not prove the whole site or its origin is healthy, and it does not mean the requested page is simply missing. A missing page is 404. A login problem is 401 or sometimes 403. Write down the full address and what you clicked before you clear anything.
Step 1: Look at the address you actually sent
- Read the address bar. A link copied from a PDF, a chat, or an email often picks up a space, a line break, or a trailing comma. Paste the address into a plain note, delete the break or the comma, and open that cleaned address once.
- If you typed it, check the spelling of the site name and the path. One wrong character is enough.
- Reload that cleaned address once. Refreshing the broken address sends the same request again.
If the address looks normal and still returns 400, compare another browser session before assigning the cause to a cookie, extension, or form.
Step 2: One private window
Open a private or incognito window and load the same cleaned address. Extensions are usually off there, and that window has no old cookies for the site. If the page loads, compare the normal window’s site data, extensions, login state, and browser settings before naming a cause. Go to the next step. If the private window also returns 400, skip the extension hunt. Try the same address on a phone, on its mobile data, not on the same Wi-Fi. If the phone also gets 400, a site-side rule or the shared address becomes more likely; send the site the address and time, without assuming either device is ruled out.
Step 3: This site’s data only
When the private window works, clear stored data for this site only. In the browser’s site settings or privacy controls, remove cookies and cached files for that one domain. Do not choose “all time” for every site. That signs you out of mail, banking, and work accounts you were not trying to fix. Reload the page. If it fails again, turn extensions off one at a time, starting with anything that rewrites pages or blocks requests. The walk for a Chrome extension that breaks one site is extensions not working. Turn the extension back on if it was not the cause.
Step 4: A form or an upload
A 400 that appears only when you submit a form or a file is that submission, not the whole site. Shorten the text, remove a character the form does not expect, or send a smaller file you already trust. Do not install an “upload fixer.” If a normal short form still returns 400 in a private window and on a phone, the site’s form is rejecting a valid try. Stop and contact the site. Include the time and the address. Do not send a screenshot of a page that shows a password.
Step 5: When you stop
You cannot repair the server’s rules from the browser. A firewall on their side, a size limit, or an application bug can answer 400 to a request that looks fine to you. Some sites also answer 400 when a login token is bad, even though 401 would be the clearer code. If signing in again does not help, that mismatch is their bug to sort. Do not edit request headers in the developer tools. A header you invent is another malformed request.
What you should be able to point at
- The address, cleaned of line breaks and stray punctuation, tried once.
- Private window result, and a phone-on-mobile-data result if the private window failed.
- Cookies cleared for this site only, and only if the private window had worked.
- One extension tested if the private window worked and site data did not.
- No header editing. No “clear all browsing data.”
Example: a line break in a copied link
A confirmation link from an email wraps in the middle of the address. The browser sends the break as a space and the site returns 400. They paste the link into a note, delete the space, and the page opens. They do not clear every cookie, and they do not refresh the broken address ten times. A 400 that appears on the phone and the laptop for a short, clean address would have been a note to the site instead of an extension test.
Related guides
Last updated: October 22, 2026
Last reviewed October 22, 2026. Suggest a correction
Questions readers ask
Is the website down?
A server or gateway answered this request with 400, but that does not prove the whole site is healthy. If every site fails to load, use the browser-loading or Wi-Fi guide.
Should I clear all cookies?
No. Clear data for the one site, and only after a private window loads it. Clearing every site signs you out of accounts that were working.
The page works in a private window.
A private-window success points to a difference in saved site data, sign-in state, extensions, or browser settings. Test one at a time and leave security software running.
I only see 400 when I submit a form.
Change that submission, or try a smaller file you already trust. If a short form fails on a phone as well, contact the site. Do not keep resubmitting the same data.
Can I fix this in the browser’s network panel?
Use that panel only to read the status. Do not rewrite headers or cookies there. A hand-edited request is easy to make worse.
Sources and methodology
Claims that depend on an outside authority are tied to the references below. Product details change. Confirm the current specification sheet before you buy or install anything.
- RFC 9110: HTTP Semantics — RFC Editor (standard), accessed October 27, 2026. Defines 400 as a request the server cannot or will not process because of a perceived client error; one response does not prove origin health.
- Delete, allow, and manage cookies in Chrome — Google Chrome Help (documentation), accessed October 27, 2026. Explains removal of cookies for a specific site; private-window success alone does not identify cookies as the cause.
Information on this site is for general educational purposes and is not professional advice.
Parent topic: Smart Home & Tech