Valentin V. Bartenev

@hongzhidao Regex support in its first implementation won't affect variables. Only pattern matching is affected. We will commit it soon (tomorrow probably).

@hongzhidao I think for variables the NJS implementation is better.

@hongzhidao It looks like layering violation that you use `*_var_*` functions for route matches. The mechanism for hashing args/headers/cookies should be more generic and separated from variables and routes. It's...

> @VBart Why not support the standard Websocket protocol? As the first step we need to support HTTP/1.1 for proxy. It's not supported yet, only HTTP/1.0.

@june07 HTTP/1.1 support was introduced with https://github.com/nginx/unit/commit/65799c7252e56d287d967bf3f036a10d5764f82c (will be released with 1.19.0 in a few weeks or so), but without keep-alive connections cache. The next step will be to introduce...

Unfortunately, there's no way to overwrite error pages in Unit right now and you have to use external solution. This feature is in the TODO list.

Currently, you can do the following steps: 1. Put a new certificate under the new name "bundle2"; 2. Switch listening socket to the new certificate (PUT "bundle2" /config/listeners/127.0.0.1:8080/tls/certificate); 3. (Optionally)...

@hongzhidao 1. The `state` directory is a blackbox. Nobody should look or touch anything inside it. All the changes must be done only using API (otherwise we will face with...

@FC-IT >but all our routes have a match for a specific host (and all listeners direct to a route) Could you provide your configuration?

@FC-IT Actually there's no Host header field in the Combined access log format, that is commonly used by web-servers (and Unit as well): https://en.wikipedia.org/wiki/Common_Log_Format The missing information in your log...