-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
求助 curl -v http://127.0.0.1:8002/static-to-header 返回Head中 无< x-echo-foo: Lua is awesome! #10
Comments
Sorry for late reply, it has been fixed in this pr #11 |
I tried the fix, but it seems still not working. I tried to add some log into echoHandler:on_response method in the echo.lua, but log didn't show up either. It seems the echo.lua didn't load successfully. I saw some error log in log of envoy, please help to check the logic.
|
@jk-tonycui it works in my test, could you show me your response headers? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
启动日志:
proxy_1 | [2022-03-28 18:01:46.954][7][debug][upstream] [external/envoy/source/common/upstream/strict_dns_cluster.cc:167] DNS refresh rate reset for web_service, refresh rate 5000 ms
curl -v http://127.0.0.1:8002/static-to-header
[root@k8s-master ~]# curl -v http://127.0.0.1:8002/static-to-header
< HTTP/1.1 200 OK
< x-powered-by: Express
< content-type: application/json; charset=utf-8
< content-length: 542
< etag: W/"21e-f89/FNAikln2H1PTo6DTuvtnrDY"
< date: Mon, 28 Mar 2022 17:55:14 GMT
< x-envoy-upstream-service-time: 22
< server: envoy
<
{
"path": "/static-to-header",
"headers": {
"host": "127.0.0.1:8002",
"user-agent": "curl/7.29.0",
"accept": "/",
"x-forwarded-proto": "http",
"x-request-id": "4f0c50fb-55d4-465d-a5f3-654a295e59d4",
"x-envoy-expected-rq-timeout-ms": "15000",
"content-length": "0"
},
"method": "GET",
"body": "",
"fresh": false,
"hostname": "127.0.0.1",
"ip": "::ffff:172.19.0.2",
"ips": [],
"protocol": "http",
"query": {},
"subdomains": [],
"xhr": false,
"os": {
"hostname": "8b9dc5e3f1f0"
}
The text was updated successfully, but these errors were encountered: