Datong Sun

> I think the root of the actual problem is that client_body_timeout is between reads. Which the nginx folks think is OK (I agree) and the openresty folks do not....

There are some typo in the variable name, and it needs to be fixed before merging.

> Technically it is possible, but we should consider the compatible issue of flavor `traditional`. @chronolaw Could you clarify why it causes compatibility issue with `traditional`? `traditional` is feature frozen...

This is a `expressions` only feature, we should not add it to `traditional` or `traditional_compatible`, they are feature frozen. cc @randmonkey

@chronolaw Is this ready for review?

Blocked by https://github.com/Kong/atc-router/pull/39.

https://github.com/dndx/nchnroutes

@vincascm This won't be an issue if the NAT device actually sends `RST` after connection tracking is broken and terminates unknown TCP mappings. Maybe this could be improved with heartbeat...

Hello @scrudge, If you use the L4 proxy functionalities provided by Kong, It should works at the L3. See: https://docs.konghq.com/2.2.x/proxy/#proxy-tcptls-traffic The reason why Kong's IP restriction plugin under HTTP mode...

What kind of client do you have? I have never seen this error before and it will be helpful if you can provide more info.