Roadmap for the OpenResty 1.19.0.1 release

[agentzh]

This issue keeps track of the next formal release, 1.19.0.1 (after 1.17.8.1 is out).

The 1.19.0.1 release is due on 5 October 2020. Version freeze will happen one month earlier. i.e., on 5 September.

• new Nginx core 1.19.0. we should use whatever being the latest release in the 1.19.x series.
• dynamically enabling SSE 4.2 only on machines with SSE 4.2 support via CPUID to make binaries compatible with old Intel CPUs as well as AMD CPUs.
• port all recent changes in lua-nginx-module over to meta-lua-nginx-module.
• switch lua-nginx-module to use the code generated by meta-lua-nginx-module.
• meta-lua-nginx-module: mini-tt2.pl: add support for emitting #line N directives to the resulting C code.
• merge test suites of lua-nginx-module, lua-resty-core, and stream-lua-nginx-module into meta-lua-nginx-module.
• new exit_worker_by_lua* directives.
• http2 streaming output support via ngx.flush(true).
• client SSL/TLS certificate support.
• ability to setting SSL ciphers and protocols on the fly.
• new aarch64 fixes in LuaJIT from Huawei engineers.
• Avoid tight version coupling among ngx_http_lua, ngx_stream_lua and lua-resty-core. We should check version requirements on the nginx module side as well so that we can still use >= VERSION instead of == VERSION

We'll keep updating this issue to always reflect the latest status.

[rainingmaster]

Hi @agentzh , could we add the feature like dynamic listen/close socket in lua? https://github.com/openresty/lua-nginx-module/issues/1690

[thibaultcha]

1. Both an important security and usability fix, https://github.com/openresty/lua-nginx-module/pull/1600 should also be a part of this roadmap imho. Not only does the currently advertised way of using OpenResty leads to virtual hosts confusion when reusing keepalive TLS-enabled connections, but the PR also offers great new dynamic capabilities for OpenResty users maintaining their own load-balancing features.
2. The new ngx_meta_luamodule I wrote here (https://github.com/openresty/meta-lua-nginx-module/pull/76) also ticks off the long pending TODO item of sharing shared dicts between the http and stream subsystems, a long requested feature for many OpenResty users. On top of that, this PR is also a first setp towards reducing code duplication, binary size, and some confusing uses of some `lua*` directives (see the PR for more info).

Both of those PRs are currently the most supported patches from the community on the GitHub repositories based on the number of +1 reactions they have received.

Lastly, as an aside, I have been maintaining a list of features to port to ngx_meta_lua (and have ported many myself already) in this issue: https://github.com/openresty/meta-lua-nginx-module/issues/70. It lists all missing ports up to the mentioned commit (last updated on 2019/08/27 as of this writing).

[agentzh]

Migrating to meta lua module and upgrading the nginx core are the main focuses for the next release. And a timely release is essential too. So we don't need to squeeze too much things into this release. We just release whatever is truly ready by the version freeze time.

[Soulou]

Is this issue obsolete?

Was there anything done for ability to setting SSL ciphers and protocols on the fly. ?

(I know ssl_client_hello primitive) but it only allows to set TLS versions not ciphers.

Thanks a lot!

[agentzh]

@Soulou We support it in our OpenResty Edge product: https://openresty.com/en/edge/ We can also offer such features as private libraries/modules under our OpenResty XRay subscription: https://openresty.com/en/xray/

[Soulou]

@Soulou We support it in our OpenResty Edge product: https://openresty.com/en/edge/ We can also offer such features as private libraries/modules under our OpenResty XRay subscription: https://openresty.com/en/xray/

Ok interesting to know, thanks for your answer