400 bad request nginx

that the nginx buffer has a bug caused by the page consumption of our site may be too large. On the Internet to find a solution, in the foreign site saw a way to increase the buffer, thoroughly solve the problem of Nginx 502 bad Gateway. The method is as follows:HTTP {...Fastcgi_buffers 8 16k;Fastcgi_buffer_size 32k;...} Increase the above two configuration it

Reason for occurrence 1, PHP fastcgi process number is not enoughWhen the Web site concurrent access is huge, the number of PHP fastcgi process is not guaranteed, because CGI is a single-threaded multi-process work, that is, CGI needs to process a page and then continue to the next page. If the number of processes is not sufficient, when the access is huge, CGI presses the request before the queue, and the subsequent

Recently Angularjs post to background 4,001 header fog without any errors.Finally found a good article, thank the authorThe solution to the "bad Request" error in SPRINGMVC (using @responsebody to process the JSON data transmitted by Ajax into the Bean)In today's development process, there was an error in the action in SPRINGMVC that processed the JSON data from the foreground AJAX

Nginx 502 Bad Gateway can be forcibly refreshed by the client, but the solution is either to change the configuration or put it on the CDN. In this case, someone found that index.html can be accessed. Because we are an online website and do not have much time to study it, this is temporary. Then, someone suggested that Ctrl + F5 should be used to refresh the cache on the server, this really solves the probl

by the page consumption of our site may be too large. On the Internet to find a solution, in the foreign site saw a way to increase the buffer, thoroughly solve the problem of Nginx 502 bad Gateway. The method is as follows: HTTP { ... Fastcgi_buffers 8 16k; Fastcgi_buffer_size 32k; ... } Increase the above two configuration items by yourself, depending on the server's already web site. Second, pr

invalid.Symptoms:1. Nginx running normally, MySQL running normally. Static HTML files can be accessed normally. Stating that Nginx service is not a problem2. Only PHP pages are not open. Error 502 Bad Getway, indicating that there is a problem between Nginx and PHP-FPM.3. Nginx's 80 port, PHP-FPM 9000 ports are runnin

set "request_terminate_timeout" to 0 s if the PHP script does not have loops or bugs. 0 s means to keep the PHP-CGI running without a time limit. And if you can't do that, that is, your PHP-CGI may have a bug, or if your bandwidth is insufficient or your PHP-CGI may be suspended for other reasons, we recommend that you assign a value to "request_terminate_timeout", which can be set based on the performance of your server. In general, the better the performance, the higher you can set, 20 minute

ServerAdmin [email protected]Documentroot/active/www/yingchao123/tradeServerName trade.test.yingchao123.comServeralias trade.yingchao123.comRewriteengine onRewriterule ^ ([\da-z]{1,10}) $./index.php?mod=listdo=uniquealias=$1 [L]Rewriterule ^ ([\da-z]{1,10}) (. +) $./index.php?mod=listdo=uniquealias=$1$2 [L]But there's a bad Request error when you write this.The workaround is to write the rewrite rule down

Today, when the project was suddenly reported a bad request error, the backstage did not have any problems.First I looked at the log log does not receive any parameters, you can determine that the request is not sent out, so it should be the foreground data submission problem.Then I saw some tips from some netizens:1. The Submission form data type does not match

In today's development process, there was an error in the action in SPRINGMVC that processed the JSON data from the foreground AJAX request directly into the corresponding entity class: The bad request, the background is not an error, 400 refers to invalid requests (the request