shreemaan-abhishek commented on issue #8768: URL: https://github.com/apache/apisix/issues/8768#issuecomment-1425647003
@WVenus we were unable to reproduce this bug. Are you using docker/kubernetes-based installation? If not, have you tried if this issue exists in docker/kubernetes based installation. We tried reproducing the bug with the go-plugin-runner and the "say" plugin. Like so: The route: ```bash curl "http://127.0.0.1:9180/apisix/admin/routes/1"; -H "X-API-KEY: edd1c9f034335f136f87ad84b625c8f1" -X PUT -d ' { "methods": ["POST"], "plugins": { "ext-plugin-pre-req": { "conf" : [ {"name": "say", "value":"{\"body\":\"hello\"}"} ] } }, "uri": "/anything/*", "upstream": { "type": "roundrobin", "nodes": { "[httpbin.org:80](http://httpbin.org/)": 1 } } }' ``` The curl post command: ```bash curl -X POST "http://127.0.0.1:9080/anything/foo?arg=10"; -F "image=@/Users/shreemaan-abhishek/Downloads/trip/IMG_4042.MOV" ``` We tried using payloads of various sizes, from KBs to several MBs. It did not fail for any size of the payload, could you report to us the payload size/length you were using? This is what we found in the logs: ```log 2023/02/10 09:43:41 [warn] 56#56: *66 [lua] init.lua:953: 2023-02-10T09:43:41.860Z INFO server/server.go:115 Client connected (unix), context: ngx.timer 2023/02/10 09:43:41 [warn] 56#56: *66 [lua] init.lua:953: 2023-02-10T09:43:41.860Z INFO server/server.go:115 Client connected (unix) 2023-02-10T09:43:41.861Z INFO server/server.go:131 receive rpc type: 1 data length: 120 2023-02-10T09:43:41.861Z INFO plugin/conf.go:98 prepare conf for plugin say, context: ngx.timer 2023/02/10 09:43:41 [warn] 56#56: *66 [lua] init.lua:953: 2023-02-10T09:43:41.871Z INFO server/server.go:131 receive rpc type: 2 data length: 476, context: ngx.timer 2023/02/10 09:43:41 [warn] 56#56: *66 [lua] init.lua:953: 2023-02-10T09:43:41.872Z INFO plugin/plugin.go:120 run plugin say, context: ngx.timer ``` -- 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]
