wfgydbu commented on issue #1970:
URL: https://github.com/apache/apisix/issues/1970#issuecomment-717059125
I actually reproduced this issue **on the same machine**.
Details steps are:
1. Setup etcd and apisix 1.5
2. Setup ssl configuration. Then there are two scenarios:
Scenario one:
Testing ordinary http or https requests.
Run`seq 1 1000 | xargs -I{} -P 20 curl -i http://127.0.0.1:9080`, work as
expected.
Run`seq 1 1000 | xargs -I{} -P 30 curl -i https://test.cn:9443 -k`, where
`test.cn` is the SNI set in admin/ssl, and 9443 is the default ssl port. work
as expected as well.
**Next.**
Scenario two:
Testing `s3cmd` with http or https.
`s3cmd` is the Command Line S3 Client and Backup tool for Linux to connect
the Amazon S3 data storage service. We use apisix as the gateway in this
scenario.
Run
`s3cmd --access_key=test --secret_key=test --host=10.10.10.40:9080
--host-bucket="10.10.10.40:9080/%(bucket)" --no-ssl --signature-v2 put file_1kb
s3://bucket`
or `s3cmd --access_key=test --secret_key=test --host="test.cn:443"
--host-bucket="test.cn:443/%(bucket)" --ssl --signature-v2 put file_1kb
s3://bucket --no-check-certificate`
respectively. Both cases will cause errors in the client side:
```
HTTP/1.1 404 Not Found
Date: Tue, 27 Oct 2020 07:16:48 GMT
Content-Type: text/plain; charset=utf-8
Transfer-Encoding: chunked
Connection: keep-alive
Server: APISIX web server
{"error_msg":"failed to match any routes"}
```
About 1/10 failure rate when testing with 20 concurrent requests.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
