Andrew Clayton

To echo @hongzhidao I'm not against the idea, but I think the location is wrong. This should really happen in the proxy code.

> npm ERR! ../nxt_napi.h:20:2: error: #error "libunit version mismatch." > npm ERR! 20 | #error "libunit version mismatch." > npm ERR! | ^~~~~ In simple terms this means the version...

> I have unit v1.32.1 installed. The latest release of `unit-http` is > v1.32.0. > Would it work if both versions match? Yes, they both **need** to be the same...

> Any reason there is not a unit-http v1.32.1 module in the npm registry? Not sure, probably an oversight, maybe @tippexs or @thresheek knows? > There should also be a...

How reproducible is this? Every request?, certain requests? Random? What does the client side look like when this happens? 5xx error response? Of course if you have a simple reproducer...

This is currently very low priority... we are currently not pushing the proxy capabilities and are concentrating on the application server side of things...

> Well, proxy capability is already there. The lack of DNS resolution is making it fairly unpractical. Of course, there are workarounds but why not just add this very important...

Given > npm ERR! gyp info spawn make npm ERR! gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ] npm ERR! In file included from ../unit.h:9, npm ERR! from ../unit.cpp:6:...

Ah, right, we don't provide nodejs language module packages for $reasons. The docs suggest that you should run `npm install -g --unsafe-perm unit-http` as root, Caveat Emptor, alternatively you can...

Some observations 1) Does it make sense to still rename ci.yml?, seeing as it isn't limited to pull-requests. 2) The last patch should just be folded into the first or...