kong.service.request.enable_buffering handler transfer-encoding:chunked lost body

[Hexiaopi]

I use kong.service.request.enable_buffering() in custom plugin
client send transfer-encoding:chunked request and server can not get request body and content-length.

kong version:2.0.4

[bungle]

@Hexiaopi can you provide us an example code? Also be specific in what you mean that server cannot get request body or content-lenght. Do you mean upstream service? And in that case, what does it get? There are a lot of limitations with ngx.location.capture that is used to implement the response buffering.

[bungle]

@Hexiaopi I will try to reproduce this tomorrow, but if you have some examples, it would be perhaps a bit faster, but I have idea that chunked responses or requests are problematic with response buffering. Perhaps both.

[Hexiaopi]

client use curl like :
curl -XPOST -H 'Transfer-Encoding: chunked' -H 'Connection: Keep-Alive' -H 'User-Agent: okhttp/3.14.0' -H 'some header' 'http://xxx.com/yyy/zzz' -d 'some json' -v

plugin use

server tcpdump

in this case server can not get content-length and http body

[bungle]

Here is my test:

curl -XPOST -H 'Transfer-Encoding: chunked' -H 'Connection: Keep-Alive' -H 'User-Agent: okhttp/3.14.0' -H 'some header' 'http://kong.test:8000/anything' -d 'some json' -v
Note: Unnecessary use of -X or --request, POST is already inferred.
*   Trying ::1:8000...
* connect to ::1 port 8000 failed: Connection refused
*   Trying 127.0.0.1:8000...
* Connected to kong.test (127.0.0.1) port 8000 (#0)
> POST /anything HTTP/1.1
> Host: kong.test:8000
> Accept: */*
> Transfer-Encoding: chunked
> Connection: Keep-Alive
> User-Agent: okhttp/3.14.0
> Content-Type: application/x-www-form-urlencoded
> 
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Content-Type: application/json
< Connection: keep-alive
< Access-Control-Allow-Origin: *
< Server: gunicorn/19.9.0
< Date: Fri, 09 Jul 2021 19:10:58 GMT
< Content-Length: 495
< Access-Control-Allow-Credentials: true
< Response-Phase: Executed
< X-Kong-Upstream-Latency: 4
< X-Kong-Proxy-Latency: 1
< Via: kong/2.4.1
< 
{
  "args": {}, 
  "data": "", 
  "files": {}, 
  "form": {
    "some json": ""
  }, 
  "headers": {
    "Accept": "*/*", 
    "Connection": "keep-alive", 
    "Content-Length": "9", 
    "Content-Type": "application/x-www-form-urlencoded", 
    "Host": "bin.test", 
    "User-Agent": "okhttp/3.14.0", 
    "X-Forwarded-Host": "kong.test", 
    "X-Forwarded-Path": "/anything"
  }, 
  "json": null, 
  "method": "POST", 
  "origin": "127.0.0.1", 
  "url": "http://kong.test/anything/anything"
}

This seems to be working

[bungle]

@Hexiaopi, Can you try Kong 2.4.1?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.