Pleas think before forking(). Do not follow Apache blindly...

Code, as is today, looks [acording to benchmarks] better then nginx, except one case !

There is fcgi in, right ? So all that additional processes are already started in the backend. If benchmarks are real no need to complicate code before some industry adoption. Of course there can be a branch to check possibilities :)

And forking is complicated and full of surprising traps. Even if they are somewhat "standard" historic Unix traps... Case study: Perl - better don't use fork there even if "threads" are in.

I wonder how zs_reverse_proxy() + SO_REUSEPORT would perform