Access error "400 Bad request": what is it and how to fix it?

Who among fans of wandering around the Internet did not encounter the error “400: Bad request” in the browser? True, not all surfers know what it means and why it arises. Now we will try to clarify this situation.

400 Bad request: what does this error mean ?

It is believed in the computer world that the error number 400 is exclusively user-defined when you enter the wrong request (URL) to access a specific site on the World Wide Web. Let us disagree with this.

400 bad request

Of course, you can enter the wrong address, but sometimes even with the correct address or the opened link, the error "HTTP: 400 Bad request" appears again and again. There can be many reasons for this. This is especially often manifested when accessing personal hosting services located on different, independent from each other servers of different providers. What is the reason?

Request syntax errors

Indeed, one of the root causes is a violation of the correctness of entering the page address. Yes, take a simple example: when trying to access the same Mail.ru mail server, a Ukrainian user can enter the URL in the address bar, as if corresponding to his region (in this case, assume that this is mail.ua).

In reality, such a site with a postal service does not exist in nature. It is clear that any Internet browser will immediately display the message “400: Bad request”. But even with this formulation of the question, you can still find a bunch of reasons for the occurrence of an access error.

Although it is generally accepted that in translation this English phrase means “bad (incorrect) request”, there are quite a few additional factors that can cause the appearance of such messages.

Error "400: Bad request Nginx" problem

The Nginx system itself is either a specific proxy mail server or a web server running on UNIX systems.

400 bad request which means

Typically, errors of this kind are associated with an incorrect server response for a request from a specific IP address. The error results are recorded in a special LOG-file, after which they are automatically entered into the firewall as unreliable. Thus, the hosting is disrupted work, regardless of which "OS" or browser used in this situation.

Firewall Impact

As already clear, the error "400: Bad request" often occurs when a request is blocked by a firewall.

The way out of this situation may be to add the address of the site or access device to the list of exceptions. For Windows-systems, this is done by accessing the security menu located in the standard “Control Panel”.

400 bad request nginx

In principle, it’s okay even to disable the firewall completely (naturally, if you have a powerful antivirus package). In this regard, some clarification is also necessary.

Antivirus Exclusion List

As a rule, the most common standard anti-virus packages have their own built-in firewall. It can also block potentially unsafe or inappropriate content.

http 400 bad request

In this situation, when the error message "400: Bad request" occurs, you should do the same as in the case described in the previous subheading.

The most necessary actions

Speaking about solving the problem with error 400, it is worth highlighting the general principles for solving such a problem. To get started, in the installed browser you just need to clear your browsing history, delete cache files and cookies. Only then can exception lists be applied.

400 bad request

By the way, after cleaning up unnecessary garbage in the browser, it is strongly recommended that you restart the computer terminal. It is likely that the problem will disappear by itself. If this does not happen, you will have to contact the provider (especially if an error occurs in all browsers). It may well be that hosting does not work or access to certain resources is blocked precisely because of malfunctions in the equipment of the provider company.

In any case, at least one of the proposed solutions to the problem, when the error "400: Bad request" occurs, should help. If this does not work, especially in the case of messages related to Nginx blocking, it is worth checking the system for viruses, because many of them are disguised specifically for this service.

In addition, it is worth checking the computer separately for adware or spyware such as Malware, Adware or Spyware with specialized software. It may well be that the unauthorized installation of some additional elements such as quick access panels and led to disruption of the system as a whole.

Source: https://habr.com/ru/post/C15795/


All Articles