Return "404 page not found" when the scheme of upstream is https

[foogao]

Hello guys,

We tried to create one route with an upstream which scheme is https, the configuration as follows

{
        "uris": [
            "/v1/services/some-uri"
        ],
        "update_time": 1698137310,
        "plugins": {
            "consumer-restriction": {
                "rejected_code": 403,
                "whitelist": [
                    "*"
                ],
                "type": "consumer_name"
            },
            "key-auth": {
                "query": "apikey",
                "header": "X-API-KEY",
                "hide_credentials": false
            },
            "proxy-rewrite": {
                "regex_uri": [
                    "^(/v1/services)/(.*)",
                    "/$2"
                ]
        },
        "upstream": {
            "scheme": "https",
            "type": "roundrobin",
            "desc": "",
            "timeout": {
                "send": 120,
                "connect": 120,
                "read": 120
            },
            "nodes": [
                {
                    "host": "node1",
                    "weight": 1,
                    "port": 443,
                    "priority": 1
                }
            ],
            "retries": 3,
            "retry_timeout": 120,
            "name": "My Service"
        },
        "methods": [
            "GET"
        ]
    }

In this route, we also added the plugin proxy-rewrite, the uri /v1/services/some-uri will be rewrite to upstream as uri /some-uri.

If the scheme is the http, the request to the uri will be successfully returned, but if we change it to https, the response status code will be 404 with content page not found.

Does anyone meet the same issue? and how to fix it?

Thanks in advance!