I understand they replaced nginx with something different. But why a half-finished webserver that doesn't even support things like URL rewriting. For those who seek a secure webserver, but with features to properly support the modern website/framework/CMS, try the Hiawatha webserver [hiawatha-webserver.org].
Because most people do not need a server full of (holes?) features... They just need to serve a few pages. Everything else is in ports, even your precious Hiawata...
No, most people want to run a simple PHP website (Wordpress, Drupal, etc). But since almost every modern CMS and framework require at least a simple form of URL rewriting (rewrite every request for a non-existig file to/index.php), OpenBSD's httpd is a no-go.
No, most people want to run a simple PHP website (Wordpress, Drupal, etc). But since almost every modern CMS and framework require at least a simple form of URL rewriting (rewrite every request for a non-existig file to/index.php), OpenBSD's httpd is a no-go.
Err... If you are running PHP on OpenBSD, you have COMPLETELY missed the point of OpenBSD in the first place.
by Anonymous Coward writes:
on Friday May 01, 2015 @08:34PM (#49598013)
OpenBSD does not care about us mortals. They are the reason why we have ASLR, PIE, 64bit, and many other features in most OSes. While the features existed, they were not pushed out by default because programs would randomly break for no apparent reason. OpenBSD took a step forward and made system designs that would cause programs that make use of undefined programming, break. This made it very easy to quickly find most flaws, allowing Linux to eventually go 64bit, among other things.
Unlike most Linux ports, much of BSD is shared among the flavors. A lot of work gets shared, even if not all at the same time. There are forks of FreeBSD explicitly forked for the purpose of security testing. They try new exciting things, if they work, they port them back to FreeBSD. You don't see this often in Linux.
New HTTP daemon (Score:2)
I understand they replaced nginx with something different. But why a half-finished webserver that doesn't even support things like URL rewriting. For those who seek a secure webserver, but with features to properly support the modern website/framework/CMS, try the Hiawatha webserver [hiawatha-webserver.org].
Re: (Score:0)
Because most people do not need a server full of (holes?) features... They just need to serve a few pages. Everything else is in ports, even your precious Hiawata...
Re: (Score:2)
Re: (Score:5, Insightful)
No, most people want to run a simple PHP website (Wordpress, Drupal, etc). But since almost every modern CMS and framework require at least a simple form of URL rewriting (rewrite every request for a non-existig file to /index.php), OpenBSD's httpd is a no-go.
Err... If you are running PHP on OpenBSD, you have COMPLETELY missed the point of OpenBSD in the first place.
Seriously, though. PHP?
Re: (Score:2)
Re:New HTTP daemon (Score:1)
Unlike most Linux ports, much of BSD is shared among the flavors. A lot of work gets shared, even if not all at the same time. There are forks of FreeBSD explicitly forked for the purpose of security testing. They try new exciting things, if they work, they port them back to FreeBSD. You don't see this often in Linux.