πŸ“„
Webhosting

Resolving Error 400 Bad Request: causes and fix

πŸ“… 12 November 2026 ✏️ 12 November 2026 ⏱ 4 min leestijd

Seeing error 400 Bad Request? Read here what the causes are and how to resolve it step by step on your website.

An error 400 Bad Request means the server cannot process your request because it is malformed. Unlike many other error messages, the cause usually does not lie with the server itself, but with the browser, cookies, URL, or submitted data. In this article you’ll read what exactly goes wrong and how to resolve the error step by step.

What does error 400 Bad Request mean

The HTTP status code 400 indicates that the server does not understand your browser’s request or considers it invalid. This happens before the server does anything substantive with the request. It therefore differs from, for example, a 404 (page not found) or a 500 (error in server processing): with a 400, the request itself is already incorrect.

Common causes

Error 400 can be caused by several things. The most common causes are:

  • Corrupt or oversized cookies in your browser, often after logging in on multiple sites or due to expired sessions.
  • An incorrectly formed URL, for example with invalid characters or a broken link.
  • A request header that is too long, for example due to accumulated cookies or an extension that adds headers.
  • An incorrectly filled-in form where required fields or expected data are missing.
  • Problems with your device’s DNS cache, causing an outdated or incorrect address to be accessed.
  • A file upload that does not meet the expected form or size.
πŸ’‘ Tip: always test the page first in an incognito window. If it works there, the problem is almost certainly in your browser’s cookies or cache.

Step-by-step plan to resolve the error

1

Clear cookies and cache

Remove the cookies and cache for the specific website via your browser settings and reload the page.

2

Check the URL

Check whether the link contains any strange characters, double slashes, or truncated parameters. Try retyping the URL manually if needed.

3

Test in another browser or incognito

This rules out the possibility that the problem lies with extensions, stored sessions, or an outdated browser cache.

4

Flush the DNS cache

Flush your device’s local DNS cache, so you’re sure you’re reaching the correct server.

5

Check the form or request

If you’re using a form or API call, check whether all required fields are filled in correctly and whether files have the correct form and size.

6

Review the server logs

As the website administrator, you can consult the error logs in Plesk to see exactly which request is being rejected and why.

Preventing error 400 on your own website

If you manage your own website and want to prevent visitors from encountering this error, pay attention to the following:

  • Keep form validation consistent between front-end and back-end, so unexpected input doesn’t lead to a rejected request.
  • Limit the number and size of cookies your website sets, especially when using many plugins or tracking scripts.
  • Make sure upload limits in your configuration match what your forms actually allow.
  • After a migration or server switch, always check that all server configuration has been correctly carried over.

If the error persists despite the steps above, it’s wise to contact your hosting provider. At Tandata, you can also look up many related error messages yourself via the knowledge base, or contact support 24/7.

Frequently asked questions

Is error 400 a problem on my end or the website’s end?

In most cases, the cause lies with your own browser, cookies, or the constructed URL. Sometimes, however, it’s due to incorrect server configuration, for example with a misconfigured redirect or form processing.

Why do I only get error 400 on one specific website?

This usually indicates accumulated or corrupt cookies for that specific website. Clear the cookies for only that domain and try again.

Can an incorrect DNS record cause an error 400?

Indirectly, yes: if you’re redirected to an incorrect or outdated IP address, the server there may reject the request. In that case, check your DNS settings.

Conclusion

Error 400 Bad Request usually arises from a malformed request: think of corrupt cookies, an incorrect URL, or an incorrectly filled-in form. By clearing cache and cookies, checking the URL, and possibly reviewing the server logs, you’ll resolve the error quickly in most cases. If the problem persists, check your server configuration or contact your hosting provider.

View web hosting β†’

Was dit artikel nuttig?