Btw, there is also specially tuned Nginx AMI: https://aws.amazon.com/marketplace/pp/B00A04GAG4/
HN user
Vidart
linux rootkit in combination with any http server
There are a lot of problems in Tengine implementation: http://mailman.nginx.org/pipermail/nginx/2012-September/0354... http://mailman.nginx.org/pipermail/nginx/2012-September/0354...
Check this comment: http://translate.googleusercontent.com/translate_c?depth=1...
It's not the "old one". Actually, the green logo was made by Igor Sysoev and it is the oldest and the only official logo.
That one from "wiki.nginx.org" is made by Cliff Wells, creator of the wiki: http://www.enemyofthestatement.com/page/view/about
btw, it's funny, @maratd who wrote "Placing communist imagery in the logo isn't amusing" doesn't even imagine that it actually was done by US citizen.
Where did you find "communist imagery in the logo"? http://nginx.org/nginx.gif
It's not a magic. It's just an optimization. Prefixed strings are organized to the radix tree for fast configuration lookup.
But the only way to deal with regexps is to execute them sequentially.
btw, the official doc is here: http://nginx.org/en/docs/http/ngx_http_core_module.html#loca...
In the link that you mentioned, ETags are produced and handled by application. There are no special needs in web-server support.