Roman Arutyunyan

We considered supporting WolfSSL a few years ago and decided not to proceed due to insufficient functionality. Probably things are different now, but it requires some research.

`h->next` only makes sense for the headers handled by a registered handler and referenced externally. For other headers the field is unused. This pattern occurs in many places across nginx...

According to the error.log, the client (device) closed the socket before sending the entire file. It's hard to tell why it did so and what kind of timeout is that....

This doesn't look right: `--with-openssl=/opt/nginx-1.26.2`. This parameter specifies a path to openssl source, while the name suggests you have specified a path to nginx source instead.

Why do you think `recv(MSG_PEEK)` can only be called once?

First, make sure you are not using OpenSSL compatibility layer, which does not support 0-RTT, see a note [here](https://nginx.org/en/docs/http/ngx_http_v3_module.html). You need to link a library other than OpenSSL, for example...

In nginx servers are grouped by listen address. Whenever you connect to a particular address, server is chosen within this group only. I don't think we want to change this.

In nginx these are separate groups and we have no plans to change this. If we change this, it would mess up existing configurations. Also, it could break them in...

Can you please explain why you need this variable. There's a variable `$status` which will be 301 in case of auto redirect.

Phases can be skipped for multiple reasons. For example, a simple `return 200 foo;` skips all phases beyond rewrite. Also, any module can install its own handler in any phase...