New answers tagged lighttpd
= > is wrong, use => (no space between the two characters)
Nginx is actually vulnerable to slowloris attack. Scarce resource is the maximum number of simultaneous worker connections. This number can be calculated as worker_connections * worker_processes and equals to 512 in default nginx configuration. So, it is quite easy to take down unprotected nginx with tools such as goloris.
The command you are looking for is semanage permissive -a httpd_t
It seems one of the WordPress plugins was causing conflicts. I turned them all off and the site started working on all browsers, then I began turning them on one by one. Fortunately the plugin causing the issue was not being used on the site so I was able to eliminate it. Do WP plugins update by themselves? This is strange because no one else has access ...
You don't generally do rewrites in nginx, the same way you do them in Apache or lighttpd. Most such things should be replaced with try_files instead. A trivial example: try_files $uri $uri/ /gi.php See the nginx documentation for more details.
You need to make sure php and php-cgi are installed, and then add the following to your lighttpd.conf fastcgi.server = ( ".php" => (( "bin-path" => "/usr/bin/php-cgi", "socket" => "/var/run/lighttpd/php.socket", "max-procs" => 2, ...
If you change url.rewrite = to url.rewrite-if-not-file = this may fix the issues you are having.
I got this working with the following rewrite rules: url.rewrite-if-not-file += ( "^/(.*)\.(css|js|jpg|png|gif)$" => "$0", "^/blog/(.*)$" => "/blog/index.php/$1" ) I hope this helps someone else running anchor cms on lighttpd
Top 50 recent answers are included