Auto Mesh配置成功后，从本地回写的http报文都无法正常回写，kt-router报499错误

Describe the bug A clear and concise description of what the bug is. 0.3.6版本 ktctl.exe mesh vr-cms-auth-server --expose 8080:80

Log please add -d to debug log router的日志如下： /docker-entrypoint.sh: /docker-entrypoint.d/ is not empty, will attempt to perform configuration /docker-entrypoint.sh: Looking for shell scripts in /docker-entrypoint.d/ /docker-entrypoint.sh: Launching /docker-entrypoint.d/10-listen-on-ipv6-by-default.sh 10-listen-on-ipv6-by-default.sh: info: /etc/nginx/conf.d/default.conf is not a file or does not exist /docker-entrypoint.sh: Launching /docker-entrypoint.d/20-envsubst-on-templates.sh /docker-entrypoint.sh: Launching /docker-entrypoint.d/30-tune-worker-processes.sh /docker-entrypoint.sh: Configuration complete; ready for start up 2022/08/09 05:59:46 [notice] 1#1: using the "epoll" event method 2022/08/09 05:59:46 [notice] 1#1: nginx/1.21.6 2022/08/09 05:59:46 [notice] 1#1: built by gcc 10.2.1 20210110 (Debian 10.2.1-6) 2022/08/09 05:59:46 [notice] 1#1: OS: Linux 5.18.9-1.el7.elrepo.x86_64 2022/08/09 05:59:46 [notice] 1#1: getrlimit(RLIMIT_NOFILE): 1048576:1048576 2022/08/09 05:59:46 [notice] 1#1: start worker processes 2022/08/09 05:59:46 [notice] 1#1: start worker process 21 2022/08/09 05:59:46 [notice] 1#1: start worker process 22 2022/08/09 05:59:46 [notice] 1#1: start worker process 23 2022/08/09 05:59:46 [notice] 1#1: start worker process 24 2022/08/09 05:59:46 [notice] 1#1: start worker process 25 2022/08/09 05:59:46 [notice] 1#1: start worker process 26 2022/08/09 05:59:46 [notice] 1#1: start worker process 27 2022/08/09 05:59:46 [notice] 1#1: start worker process 28 2022/08/09 05:59:52 [notice] 1#1: signal 1 (SIGHUP) received from 29, reconfiguring 2022/08/09 05:59:52 [notice] 1#1: reconfiguring 2022/08/09 05:59:52 [notice] 1#1: using the "epoll" event method 2022/08/09 05:59:52 [notice] 1#1: start worker processes 2022/08/09 05:59:52 [notice] 1#1: start worker process 39 2022/08/09 05:59:52 [notice] 1#1: start worker process 40 2022/08/09 05:59:52 [notice] 1#1: start worker process 41 2022/08/09 05:59:52 [notice] 1#1: start worker process 42 2022/08/09 05:59:52 [notice] 1#1: start worker process 43 2022/08/09 05:59:52 [notice] 1#1: start worker process 44 2022/08/09 05:59:52 [notice] 1#1: start worker process 45 2022/08/09 05:59:52 [notice] 1#1: start worker process 46 2022/08/09 05:59:52 [notice] 25#25: gracefully shutting down 2022/08/09 05:59:52 [notice] 24#24: gracefully shutting down 2022/08/09 05:59:52 [notice] 21#21: gracefully shutting down 2022/08/09 05:59:52 [notice] 28#28: gracefully shutting down 2022/08/09 05:59:52 [notice] 26#26: gracefully shutting down 2022/08/09 05:59:52 [notice] 24#24: exiting 2022/08/09 05:59:52 [notice] 28#28: exiting 2022/08/09 05:59:52 [notice] 21#21: exiting 2022/08/09 05:59:52 [notice] 25#25: exiting 2022/08/09 05:59:52 [notice] 26#26: exiting 2022/08/09 05:59:52 [notice] 28#28: exit 2022/08/09 05:59:52 [notice] 24#24: exit 2022/08/09 05:59:52 [notice] 21#21: exit 2022/08/09 05:59:52 [notice] 26#26: exit 2022/08/09 05:59:52 [notice] 25#25: exit 2022/08/09 05:59:52 [notice] 27#27: gracefully shutting down 2022/08/09 05:59:52 [notice] 23#23: gracefully shutting down 2022/08/09 05:59:52 [notice] 27#27: exiting 2022/08/09 05:59:52 [notice] 23#23: exiting 2022/08/09 05:59:52 [notice] 22#22: gracefully shutting down 2022/08/09 05:59:52 [notice] 22#22: exiting 2022/08/09 05:59:52 [notice] 22#22: exit 2022/08/09 05:59:52 [notice] 27#27: exit 2022/08/09 05:59:52 [notice] 23#23: exit 2022/08/09 05:59:52 [notice] 1#1: signal 17 (SIGCHLD) received from 27 2022/08/09 05:59:52 [notice] 1#1: worker process 23 exited with code 0 2022/08/09 05:59:52 [notice] 1#1: worker process 27 exited with code 0 2022/08/09 05:59:52 [notice] 1#1: signal 29 (SIGIO) received 2022/08/09 05:59:52 [notice] 1#1: signal 17 (SIGCHLD) received from 23 2022/08/09 05:59:52 [notice] 1#1: signal 17 (SIGCHLD) received from 24 2022/08/09 05:59:52 [notice] 1#1: worker process 24 exited with code 0 2022/08/09 05:59:52 [notice] 1#1: signal 29 (SIGIO) received 2022/08/09 05:59:52 [notice] 1#1: signal 17 (SIGCHLD) received from 22 2022/08/09 05:59:52 [notice] 1#1: worker process 22 exited with code 0 2022/08/09 05:59:52 [notice] 1#1: signal 29 (SIGIO) received 2022/08/09 05:59:52 [notice] 1#1: signal 17 (SIGCHLD) received from 28 2022/08/09 05:59:52 [notice] 1#1: worker process 28 exited with code 0 2022/08/09 05:59:52 [notice] 1#1: signal 29 (SIGIO) received 2022/08/09 05:59:52 [notice] 1#1: signal 17 (SIGCHLD) received from 26 2022/08/09 05:59:52 [notice] 1#1: worker process 21 exited with code 0 2022/08/09 05:59:52 [notice] 1#1: worker process 26 exited with code 0 2022/08/09 05:59:52 [notice] 1#1: signal 29 (SIGIO) received 2022/08/09 05:59:52 [notice] 1#1: signal 17 (SIGCHLD) received from 25 2022/08/09 05:59:52 [notice] 1#1: worker process 25 exited with code 0 2022/08/09 05:59:52 [notice] 1#1: signal 29 (SIGIO) received 10.42.7.81 - - [09/Aug/2022:06:01:21 +0000] "POST /oauth/token HTTP/1.1" 499 0 "-" "-" "192.168.99.19, 10.42.3.0" Environment (please complete the following information):

OS: windows7
Kubernetes 1.17.5
KT Version 0.3.6 ktctl命令行的日志： ktctl.exe mesh vr-cms-auth-server --expose 8080:80 --versionMark gyy-test --debug 2:10PM DBG Background task log to C:\Users\lucky\AppData\Local\Temp\kt-317039456 6 2:10PM INF Using cluster context local (local) 2:10PM INF KtConnect 0.3.6 start at 12076 (windows amd64) 2:10PM DBG Rectify pod kt-rectifier-ivvte created 2:10PM INF Fetching cluster time ... 2:10PM DBG Execute command [date +%s] in kt-rectifier-ivvte:standalone 2:10PM DBG No time difference 2:10PM DBG Service target ports: [80] 2:10PM INF Using auto mode 2:10PM INF Service vr-cms-auth-server locked 2:10PM INF Service vr-cms-auth-server-kt-stuntman created 2:10PM INF Service vr-cms-auth-server-kt-mesh-gyy-test created 2:10PM INF Router pod vr-cms-auth-server-kt-router created 2:10PM INF Waiting for pod vr-cms-auth-server-kt-router ... 2:10PM INF Waiting for pod vr-cms-auth-server-kt-router ... 2:10PM INF Waiting for pod vr-cms-auth-server-kt-router ... 2:11PM INF Waiting for pod vr-cms-auth-server-kt-router ... 2:11PM INF Pod vr-cms-auth-server-kt-router is ready 2:11PM INF Router pod is ready 2:11PM DBG Execute command [/usr/sbin/router setup vr-cms-auth-server 80:80 vers ion:gyy-test] in vr-cms-auth-server-kt-router:standalone 2:11PM DBG Stdout: 2:11PM DBG Stderr: 6:11AM INF Route setup completed. 2:11PM INF Router pod configuration done 2:11PM DBG Private Key generated 2:11PM DBG Public key generated 2:11PM INF Successful create config map vr-cms-auth-server-kt-mesh-gyy-test 2:11PM INF Deploying shadow pod vr-cms-auth-server-kt-mesh-gyy-test in namespace default 2:11PM INF Waiting for pod vr-cms-auth-server-kt-mesh-gyy-test ... 2:11PM INF Pod vr-cms-auth-server-kt-mesh-gyy-test is ready 2:11PM INF Forwarding pod vr-cms-auth-server-kt-mesh-gyy-test to local via port 8080:80 2:11PM DBG Using port 53649 2:11PM DBG Request port forward pod:22 -> local:53649 via https://192.168.201.13 6:6443 2:11PM INF Port forward local:53649 -> pod vr-cms-auth-server-kt-mesh-gyy-test:2 2 established 2:11PM DBG Forwarding 127.0.0.1:53649 to local endpoint 0.0.0.0:80 via 127.0.0.1 :8080 2:11PM INF Reverse tunnel 0.0.0.0:80 -> 127.0.0.1:8080 established 2:11PM INF --------------------------------------------------------------- 2:11PM INF Now you can access your service by header 'VERSION: gyy-test' 2:11PM INF --------------------------------------------------------------- 2:11PM INF Service vr-cms-auth-server unlocked 2:11PM DBG Service vr-cms-auth-server modified Additional context Add any other context about the problem here.

alibaba / kt-connect

Auto Mesh配置成功后，从本地回写的http报文都无法正常回写，kt-router报499错误 #348