nanamikon commented on issue #4875: URL: https://github.com/apache/apisix/issues/4875#issuecomment-904256845
+1， but I think 2.5 has fixed this by upgrade lua-resty-http to latest version（0.16.1） ``` -rw-r--r-- 1 jianzhou staff 57956 Aug 23 12:02 argparse.lua -rw-r--r-- 1 jianzhou staff 7126 Aug 23 12:02 base64.lua -rw-r--r-- 1 jianzhou staff 12069 Aug 23 12:01 binaryheap.lua -rw-r--r-- 1 jianzhou staff 22416 Aug 23 12:02 dkjson.lua drwxr-xr-x 11 jianzhou staff 352 Aug 23 12:02 graphql drwxr-xr-x 3 jianzhou staff 96 Aug 23 12:02 jsonschema -rw-r--r-- 1 jianzhou staff 42889 Aug 23 12:02 jsonschema.lua -rw-r--r-- 1 jianzhou staff 8331 Aug 23 12:02 ltn12.lua drwxr-xr-x 5 jianzhou staff 160 Aug 23 17:31 lua_resty_http_0_16_1_0-resty drwxr-xr-x 3 jianzhou staff 96 Aug 23 12:02 lua_resty_jwt_0_2_0_0-resty -rw-r--r-- 1 jianzhou staff 1602 Aug 23 12:01 luaxxhash.lua -rw-r--r-- 1 jianzhou staff 2487 Aug 23 12:02 mime.lua drwxr-xr-x 3 jianzhou staff 96 Aug 23 12:02 net drwxr-xr-x 6 jianzhou staff 192 Aug 23 12:02 opentracing drwxr-xr-x 41 jianzhou staff 1312 Aug 23 12:03 pl -rw-r--r-- 1 jianzhou staff 28754 Aug 23 12:02 prometheus.lua -rw-r--r-- 1 jianzhou staff 3371 Aug 23 12:02 prometheus_keys.lua -rw-r--r-- 1 jianzhou staff 2212 Aug 23 12:02 prometheus_resty_counter.lua -rw-r--r-- 1 jianzhou staff 32027 Aug 23 12:02 protoc.lua -rw-r--r-- 1 jianzhou staff 6450 Aug 23 12:02 re.lua drwxr-xr-x 36 jianzhou staff 1152 Aug 23 17:30 resty drwxr-xr-x 13 jianzhou staff 416 Aug 23 12:02 skywalking drwxr-xr-x 8 jianzhou staff 256 Aug 23 12:02 socket -rw-r--r-- 1 jianzhou staff 4451 Aug 23 12:02 socket.lua drwxr-xr-x 3 jianzhou staff 96 Aug 23 12:02 ssl -rw-r--r-- 1 jianzhou staff 8126 Aug 23 12:02 ssl.lua -rw-r--r-- 1 jianzhou staff 19180 Aug 23 12:02 tinyyaml.lua -rw-r--r-- 1 jianzhou staff 2637 Aug 23 12:01 typeof.lua ``` Maybe I should copy all files in the lua_resty_http_0_16_1_0-resty to parent dir? -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
