Hot answers tagged lighttpd
3
Yes, it's possible to download the entire repository contents (including history) – a simple git clone would do it. However, this assumes someone knew about the existence of that .git directory...it's more likely that nobody has even noticed it. You can always check your web server's logs to be sure.
2
I retrieved the doc of lighttpd's mod_alias module. I bet you have a problem with the trailing slashes. Be sure that all alias entries end with a slash:
alias.url = (
"/acruz/" => "/var/www/localhost/htdocs/acruz/",
"/jvangemeren/" => "/var/www/localhost/htdocs/jvangemeren/",
"/doceno/" => "/var/www/localhost/htdocs/doceno/"
)
...
1
The simplest alternative is not to run a web server at all. This generally makes little difference in the browser, compared to returning an empty page.
Otherwise, lightweight web servers available through MacPorts include Abyss, Cheetah, Lighttpd, LWS, Mathopd, Mongoose, Monkeyd, Pico Server, Webfs, … It's hard to give a specific recommendation since you ...
1
In Apache you can define patterns (similar to mod_cgi) which designate requests sent to FastCGI applications. Mod_fcgid is a FastCGI process manager, spawning each unique application with a specific permissions (suexec).
This is not possible with lighttpd. Lighttpd does not have a FastCGI process manager, which can change permissions, built-in (which is ...
1
What I do in this situation is have a small one-page site available through HTTP that contains a single page with a meta refresh tag and possibly an explanation for browsers that have redirects disabled or unsupported for some reason. Create a custom 404 error page that also does the same thing.
The meta tag should then redirect to https://127.0.0.1 or ...
1
2 options:
put something like this into your lighttpd.conf:
server.port = 8000
launch lighttpd with admin-rights via sudo:
$> sudo lighttpd -f lighttpd.conf -D
Also read the lighthttpd configuration tutorial.
1
One option is to change the network adaptor of the virtual machine to bridged mode; you should then be able to access the virtual server from the other machines on the network, by providing your guest's IP address.
Edit:
For practical aspects, look at the VirtualBox documentation on Virtual networking. Your options are to use bridged networking
With ...
1
Looks like an SELinux issue. You could temporarily disable SELinux and test this theory. Try executing on the command line
sudo echo 0 >/selinux/enforce
and then restart lighttpd. See if it works. If it doesn't work, it isn't an SELinux issue. Reboot the machine to re-enable SELinux or execute:
sudo echo 1 >/selinux/enforce
If it does fix it, you ...
1
Well, it was the bin-path setting that I was getting hung up on. My application resides now at:
/var/www/localhost/cgi-bin/tiny.fcgi
The socket is created at:
/var/run/lighttpd/tiny.socket-1 (the '-1' is created by spawn-fcgi, and it's chmod'd so lighttpd can r/w to it)
The mod_fcgi.conf file:
server.modules += ("mod_fastcgi")
fastcgi.debug = 1
...
1
http://redmine.lighttpd.net/projects/1/wiki/docs_modredirect
$HTTP["host"] !~ "^(www\.)?dontredirect\.com.*$" {
url.redirect = (
"^/(.*)" => "http://www.redirected.com/$1"
)
}
Not too difficult, reading the above page would have taken only 1 minute. google is your friend.
Only top voted, non community-wiki answers of a minimum length are eligible
