PHP max_input_var to the 1000 result in unacceptable when too many post array parameter value back
Gree afternoon suddenly received a phone call saying not to set bulk stores task, but can not reproduce in a test environment, test environment properly.
Then log on to a production environment, choose a few to save is normal. But when all submissions will die, num parameter can not receive the background
I analyzed the incoming message, there is this parameter, but can not get back, this is very strange. In the production environment to debug breakpoint hit, I did not see what was happening.
Noticed the back post when viewing the source code over the array only 999
There is no coincidence ah, only 999 stores? Go backstage looked at, there are more than two thousand stores
The problem is to locate, but why are so many pieces of data can not post it?
The first form of enctype default application / x-www-form-urlencoded. I think that because of this law can only pass pass within 1000, it changed multipar / form-data. The problem is not solved
Then Baidu oriented programming. Check the information, I found that there is a php configuration max_input_var is to limit the number of input. I put this into a 10000. Submit, success, ha, more than three hours so passed.
to sum up:
There are many configuration items in the php configuration file. Understanding these configuration items can help you tune php. And can solve a lot of strange questions.
A similar configuration are:
max_execution_time = 600
max_input_time = 600
memory_limit = 32m
file_uploads = on
upload_tmp_dir = / tmp
upload_max_filesize = 32m
post_max_size = 32m
In nginx in a similar configuration are:
keepalive_timeout 60;
send_timeout 3m;
client_max_body_size 500m;
nginx and php configuration often associated together to tune