Then, send a request and get a wrong result HTTP/1.1 400 Bad Request.
By reading the code and nginx docs, I find the switch ssl_asynch is designed by a similar mechanism to ssl on/off. Maybe we should make sure the above configuration can work.Another reason is that some times there are many server int http block.
Test case:
①
We get the right result of the test cases blow in ① 、 ② 、③、④
curl -svo /dev/null https://test.async.nginx:443/index.html --resolve test.async.nginx:443:127.0.0.1 -k
curl -svo /dev/null https://test.async.nginx:4433/index.html --resolve test.async.nginx:4433:127.0.0.1 -k
We also get the right result of test case below in ① and ②
curl -vo /dev/null http://test.async.nginx/index.html -x 127.0.0.1:80
But because of the switch ssl on/off we can’t get right result in ③ and ④;Maybe we could let it be or fix it in the project “nginx”
curl -vo /dev/null http://test.async.nginx/index.html -x 127.0.0.1:80
Then, send a request and get a wrong result HTTP/1.1 400 Bad Request. By reading the code and nginx docs, I find the switch ssl_asynch is designed by a similar mechanism to ssl on/off. Maybe we should make sure the above configuration can work.Another reason is that some times there are many server int http block. Test case: ①
②
③
④
We get the right result of the test cases blow in ① 、 ② 、③、④ curl -svo /dev/null https://test.async.nginx:443/index.html --resolve test.async.nginx:443:127.0.0.1 -k curl -svo /dev/null https://test.async.nginx:4433/index.html --resolve test.async.nginx:4433:127.0.0.1 -k We also get the right result of test case below in ① and ② curl -vo /dev/null http://test.async.nginx/index.html -x 127.0.0.1:80
But because of the switch ssl on/off we can’t get right result in ③ and ④;Maybe we could let it be or fix it in the project “nginx” curl -vo /dev/null http://test.async.nginx/index.html -x 127.0.0.1:80