Yichun Zhang

@amgorb You know that your `log_by_lua_block` directive will also get inherited by your `location /back` which does not have any upstream facilities (like `proxy_pass`) configured? Your `error` message is for...

@itpp16 Because you didn't provide enough info, I can only guess here. This error message means two possibilities usually: 1. You didn't compile the ngx_http_lua module as a static module...

@itpp16 It cannot be. The `_ngx_http_lua_get_request` symbol is from ngx_http_lua_module and apparently your linker cannot find it due to the lack of ngx_http_lua_module. The same applies to `_ngx_http_lua_add_package_preload`.

Hi guys. Thanks for contributing. I've found so many coding style issues in this patch. So many that I'm tired of commenting in the patch. Please fix them before I...

Since adding add/remove peers is inevitably hacky, I wonder if the upcoming `balancer_by_lua` directive in ngx_lua will fulfil your requirements. Basically we will allow using Lua to write nginx upstream...

@wangfakang least_conn and ip_hash assume the round-robin upstream module at the bottom. Since balancer_by_lua can replace round-robin altogether, I need to think more about getting existing upstream modules work with...

@wangfakang Yeah, that was the goal of `balancer_by_lua`. We needed for per-request load balancing policies at CloudFlare. It would be out in next 2 months or so.

@aledbf Now it's recommended to use `balancer_by_lua*` for such kind of things.

yeah, we'll look into it. Thanks for the reminder.

@siddhesh Sorry I just saw this one. I agree with formal new releases. We'd think more about release number scheme though. We are currently using version numbers like v2.1-20190510. I'm...