Jinhua Tan

@starwing Hi, I meet this problem too, and it seems this should be legal? https://developers.google.com/protocol-buffers/docs/proto3#reserved_values. And it is worked under golang: ``` enum Foo { reserved 2, 15, 9 to...

@harijvs6 hi, could you add some test cases for this PR?

@Mike-LiWeiZhong hello, what is the whitelist you refer to? iptables or `deny`/`allow` in Nginx?

@agentzh @thibaultcha Hello, How is this PR going? I think this function is great, allowing us to use only one upstream block, but manage our own connection pool according to...

@doujiang24 @spacewander hihi, could you help to have a look together. And I think we can support the connection limit to upstream(like backlog in ngx.tcp.socket) base on this feature in...

Hi @mikz Sorry for our delay I think this PR is good for us to share a counter for difference rate limit policy, just like [limit:conn](https://github.com/openresty/lua-resty-limit-traffic/blob/master/lib/resty/limit/conn.lua#L58). And could you split...

@juzipeek Hi, Thanks for your commit. I think we should update the [new methond](https://github.com/openresty/lua-resty-lrucache#new) in README too?

> when i download v0.27 it is all right Hello, could you reproduct your problems again, and print the `err`? There should be more detail in the `err`.

@agentzh [run `ngx.exit()` first time in `body_filter`](https://github.com/openresty/lua-nginx-module/pull/1009/files#diff-a6f1336f42adee1a8437f5073832da13R159) will return `NGX_OK` because I think we should use follow body_filter to filter the output buffer， and [`NGX_ERROR` will be return](https://github.com/openresty/lua-nginx-module/pull/1009/files#diff-a6f1336f42adee1a8437f5073832da13R275) while `ctx.body_exited`...

@agentzh Should we judge the `rc` is `ngx.ERROR` or the argument is a code no smaller than 400 [here](https://github.com/openresty/lua-nginx-module/pull/1009/files#diff-198bce3a7eb5e4a6fdc54aae29b46483R492)? However, this status code cannot be response to the client, so...