Who lovers wander through the expanses of the Internet are not faced with the advent of the browser error "400: Bad request»?However, not all surfers know what it means and why occurs.Now we shall try to clarify the situation.
400 Bad request: What does this error?
It is believed in the computer world, the error at No. 400 is merely a custom character with the introduction of improper request (URL-address) for access to a particular site on the World Wide Web.We will dare to disagree.
Of course, you can enter an incorrect address, but sometimes even at the right address or open the link error «HTTP: 400 Bad request» appears again and again.The reasons for this can be many.This is especially evident when accessing personal hosting, placed on different, independent servers of different providers.What is the reason?
query syntax errors
Indeed, one of the root causes can be called a violation of the correctness of the address input page.Yes, to take a simple example: when you try to access the same e-mail server Mail.ru Ukrainian user can enter in the address bar URL, like its corresponding region (in this case, we assume that this address mail.ua).
In fact, such a site with the postal service does not exist in nature.It is clear that any Internet browser immediately displays the message "400: Bad request».But even with this approach, you can find another bunch of causes of access errors.
Although it is assumed that in the translation of an English phrase means "a bad (invalid) inquiry," there are many other factors that can cause the appearance of such messages.
problem error "400: Bad request Nginx»
The system Nginx is a specific mail server or a proxy or web server running under UNIX-systems.
Generally, such errors are related to the wrong server response to a request from a particular IP-address.The results of errors found in the special LOG-file is then automatically entered in the firewall as unreliable.Thus, hosting disrupted, no matter what, "Operating System" or the browser used in this situation.
Impact Firewall
As is clear, the error "400: Bad request» often occurs when a firewall blocking requests.
way out of this situation may be entering website address, or device access to the exceptions list.For Windows-based systems, this is done by accessing the menu system security is in the standard "Control Panel."
In principle, there is nothing wrong even to disable the firewall completely (of course, if there is a powerful anti-virus package).On this account, too, need to give some explanations.
list of exceptions antivirus
As a rule, the most common full-time anti-virus package has its own built-in firewall.It can also block potentially unsafe or unwanted content.
In this situation, when an error message "400: Bad request» should do the same, as in the case described in the previous subtitle.
most appropriate action
talking about solving the problem with an error 400 is to provide general principles for the solution of such problems.To get started in your browser, you just need to set clean history of visits, delete the cache files and cookies.Only then can apply exclusion lists.
Incidentally, after the cleaning of unnecessary waste 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, it is necessary to communicate with your ISP (especially if there is the appearance of an error on all browsers).It may well be that not working hosting or blocked access to certain resources is due to a problem with your equipment provider company.
In any case, at least one of the proposed solutions to the problem when there is an error "400: Bad request», should help.If that does not work, especially in the case of a message associated with blocking Nginx, it's worth checking your system for viruses, many of them masked it under this service.
In addition, it is necessary to separately examine the computer to determine the presence of advertising or spyware such as Malware, Adware or Spyware specialized software.It may well be that the unauthorized installation of any additional elements such as the Quick Access Toolbar, and led to the disruption of the system as a whole.
