Re:Optionsbleed – HTTP OPTIONS method can leak Apache's serv...
by wolco on Monday September 18, 2017 @11:44AM
(#15276889)
Speed is one of the reasons to stay on apache. Using nginx to serve static and using php_mod vs fpm-php will be faster as long as you disable directory level .htaccess
[ Parent
| on HN ]
Re:Optionsbleed – HTTP OPTIONS method can leak Apache's serv...
by pmlnr on Monday September 18, 2017 @11:56AM
(#15276990)
If you're using php-fpm over unix socket, I doubt this is true, please show some stats.
Re:Optionsbleed – HTTP OPTIONS method can leak Apache's serv...
by Veratyr on Monday September 18, 2017 @12:50PM
(#15277448)
Does this apply to anything other than PHP? Not saying it's not significant, just curious. Does mod_wsgi outperform uwsgi with uwsgi_pass for example?
Re:Optionsbleed – HTTP OPTIONS method can leak Apache's serv...
by Thaxll on Monday September 18, 2017 @12:55PM
(#15277507)
Nginx is faster than Apache, you're talking about PHP which is very different. php-fpm is not part of Nginx.
Re:Optionsbleed – HTTP OPTIONS method can leak Apache's serv...
by xorcist on Monday September 18, 2017 @01:12PM
(#15277651)
Nginx should be faster in theory, but it's kind of hard to show in practice as the actual http parsing is just so much faster than anything else. You have to really tune them for for benchmark scenarios to see any kind of difference.
What your vendor supports and what you are most comfortable with configuring should decide which one you run.
PHP, as you say, is something else entirely. It's so much slower than your http server so the latter doesn't matter at all.