Skip to content
OSULZER.AT

Is my website down?

Error 400: Bad Request

Is it your browser or the website? Check right here whether the site responds normally for everyone else.

Checks the status code, every redirect, the variants with and without www and over http and https, the SSL certificate and the response time.

Free, no sign-up - no data about you is stored.

Technical finding without guarantee. The check runs once from a server in Germany. If your website is only unreachable from certain networks or countries, the result may differ.

What does Error 400 mean?

A 400 Bad Request means the server considers the request malformed and won't process it at all. Unlike a 500, nothing has crashed, the server is simply rejecting what it received.

Often the cause is on the visitor side, or more precisely in their browser: too many or too large cookies, a broken URL or a faulty upload. Then only some people see the error while the site works for everyone else. nginx often shows "400 Bad Request - Request Header Or Cookie Too Large" in this case.

If the site also returns 400 in the checker here, the problem is the server or the application itself, for example a rule that rejects certain requests across the board.

Common causes.

  • Oversized cookies

    Shops, tracking and consent tools set lots of cookies. Once together they exceed the server limit, every request from that browser is rejected.

  • Malformed URL

    Invalid characters, badly encoded special characters or a link cut off in an email can make a request invalid.

  • Stale browser cache

    Stored data no longer matches the current version of the site, for example after a rebuild or domain change.

  • Upload too large

    Some servers answer oversized files with 400 instead of the more fitting 413 Payload Too Large.

  • Invalid API request

    If required fields are missing or the format is wrong, an API responds with 400. This mostly affects forms and integrations.

With WordPress and hosting.

On WordPress sites with WooCommerce, several tracking tools and a cookie banner, cookies grow quickly. A typical sign is that only admins or regular customers see the error, because they've collected the most. The size limit for request headers is set in the nginx or Apache config, and on shared hosting only the host can change it.

If the 400 only appears when submitting a form or saving in the editor, look at security plugins and the hosting firewall, which may flag certain content as an attack. Proxies that modify headers on the way can also cause a 400.

How to fix it.

  1. Compare with the checker

    If the checker above returns 200, the site works in principle and the problem is your browser. If it returns 400, the server is the issue.

  2. Delete the site's cookies

    In your browser settings, delete cookies and site data for this one domain only. That fixes the most common case on the spot.

  3. Check the URL

    Type the address again instead of copying a long link. Watch out for special characters, spaces and parts that got cut off.

  4. Try a private window or another browser

    If it works there, cookies, cache or a browser extension are to blame.

  5. Reduce cookies on the site

    If many visitors are affected, check which plugins and tracking services set large or numerous cookies, and clean up.

  6. Have the server limit raised

    If that's not enough, your host can increase the request header limit. That's a web server setting, not something in WordPress.

Impact on Google.

Googlebot doesn't send cookies, so the most common 400 case doesn't affect it. If a page returns 400 to Google as well, though, Google treats it like a page that doesn't exist: it won't be indexed or drops out of the index. Check the Pages report in Search Console for URLs with 4xx errors.

Good to know

Questions about Error 400?

The most common questions, answered briefly.

Questions about Error 400

Is a 400 my fault or the website?

Usually your browser, if others can see the site normally. If the checker here shows a 400 too, the website or server is the problem.

Will I lose data if I delete the cookies?

If you only delete cookies for this one site, you'll be logged out there and a shopping cart may be empty. Other websites aren't affected.

What does "Request Header Or Cookie Too Large" mean?

That's nginx's 400 message when a request's cookies or headers are bigger than allowed. Deleting the site's cookies helps for now, the lasting fix is setting fewer cookies or raising the server limit.

All status codes at a glance.

2xx: Success

  • 200OKAll good: the server understood the request and delivers the page.
  • 201CreatedThe request succeeded and created something new, for example a record via an API.
  • 204No ContentSuccessful, but the response has no body. Typical for APIs and background requests, not for regular pages.

3xx: Redirects

4xx: Client errors

5xx: Server errors

No status code: connection errors

New project?

Contact.

Tell me briefly about your project - I'll get back to you personally.

Your data is used solely to handle your inquiry. More in the privacy policy.