400 bad request error on the Internet

400 bad request error occurs on the Internet to solve the problem: when the computer is connected to the Internet, the interface suddenly fails to be opened, and the interface displays the error 400 bad request. Sometimes the firewall is shut down and can last for several minutes, but it will not work again later. The above error persists. Solution: 1. When this error occurs, the first thought is a server error. The domain name is resolved incorrectly, so I checked the DNS server configuration. No error. Step 2 is started. 2. Baidu used this error code to access the Internet. There are different comments from various netizens, But they basically say that the cookie of IE is fixed. The reason is that the http request header is too long, which leads to this error. The solution for some netizens is referenced below (1) 1. Check whether the internet Explorer settings are faulty. You can delete the cookies and Temporary internet Files of internet Explorer first. Open IE, Click Tools-internet Options on the top menu bar, click Delete files on general options, and switch to advanced-Restore advanced settings ], restore the original settings. Is it possible to solve the 400 bad request fault on the webpage when you try to open the browser. (2) Use anti-virus software for repair. For example, 360 of the security guard system is repaired, and then the computer is restarted. Neither of the above solutions solved my problem. The problems they explained were all based on IE browsers. 3. check whether the 360 browser caused by Internet Explorer is also the IE kernel, so there is no need to test it. Therefore, you can only choose Firefox browser to open the webpage again and find that it is also a 400 bad request error, therefore, the problem from Baidu is clearly not what I encountered. Since it is not a browser issue, it must be a network issue. 4. Open QQ, Renren and other software, and you can log on when you discover it. That is to say, the network can be connected. QQ is based on UDP protocol. Therefore, the network protocol should be damaged by viruses or other software. Finally, I fixed the issue by referring to a netizen's blog. Cmd, enter the console program: Enter netsh winsock restart. Then restart the computer. OK. After several hours, I finally got it done. Winsock is an application layer service that provides high-level data transmission programming interfaces unrelated to the underlying transmission protocol. Netsh is an interface that can operate on almost all network connection settings through command lines, such as setting IP addresses, DNS, network cards, and wireless networks.