lighttpd 1.4.19 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News lighttpd 1.4.19 (Default branch)
# 1  
Old 03-11-2008
lighttpd 1.4.19 (Default branch)

Image lighttpd is a secure, fast, compliant, and very flexible Web server which has been optimized for high-performance environments. It has a very low memory footprint compared to other Web servers, and it takes care of CPU load. It has an advanced feature set that includes FastCGI (load balanced), CGI, Auth, Output-Compression, URL-Rewriting, SSL, and much more. License: BSD License (revised) Changes:
One major (core) and two minor security issues (mod_cgi, mod_userdir) were fixed along with many bugs. Compilation and the test suite now pass cleanly on Solaris. SSL support should result in fewer warnings and If-Range is now honored.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

2 More Discussions You Might Find Interesting

1. Debian

Vulnerable to symlink attack notice while trying to upgrade lighttpd.

I got this while I tried to upgrade my server and have been unable to find any explanations for what I could do while I have searched after an solution. I were an bit uncertain about how to search for an answer and have tried with some searches that I think should have been good enough as well with... (2 Replies)
Discussion started by: Jonathan Sander
2 Replies

2. Debian

Lighttpd problem

Hi please help, sudden problem. (Without modification) My server ~ 3-4 days ago, daily 4-5x timeout problem (slow loading my website). Always the problem occurs every 4 hours!!! (No cronjob) 5500-28000 ms loading time 2-3 minutes and after resolves. 3-4 days before anything about not set the... (10 Replies)
Discussion started by: nenmart
10 Replies
Login or Register to Ask a Question
Plack::Middleware::LighttpdScriptNameFix(3pm)		User Contributed Perl Documentation	     Plack::Middleware::LighttpdScriptNameFix(3pm)

NAME
Plack::Middleware::LighttpdScriptNameFix - fixes wrong SCRIPT_NAME and PATH_INFO that lighttpd sets SYNOPSIS
# in your app.psgi use Plack::Builder; builder { enable "LighttpdScriptNameFix"; $app; }; # Or from the command line plackup -s FCGI -e 'enable "LighttpdScriptNameFix"' /path/to/app.psgi DESCRIPTION
This middleware fixes wrong "SCRIPT_NAME" and "PATH_INFO" set by lighttpd when you mount your app under the root path ("/"). If you use lighttpd 1.4.23 or later you can instead enable "fix-root-scriptname" flag inside "fastcgi.server" instead of using this middleware. CONFIGURATION
script_name Even with "fix-root-scriptname", lighttpd still sets weird "SCRIPT_NAME" and "PATH_INFO" if you mount your application at "" or something that ends with "/". Setting "script_name" option tells the middleware how to reconstruct the new correct "SCRIPT_NAME" and "PATH_INFO". If you mount the app under "/something/", you should set: enable "LighttpdScriptNameFix", script_name => "/something"; and when a request for "/something/a/b?param=1" comes, "SCRIPT_NAME" becomes "/something" and "PATH_INFO" becomes "/a/b". "script_name" option is set to empty by default, which means all the request path is set to "PATH_INFO" and it behaves like your fastcgi application is mounted in the root path. AUTHORS
Yury Zavarin Tatsuhiko Miyagawa SEE ALSO
Plack::Handler::FCGI <http://github.com/miyagawa/Plack/issues#issue/68> <https://redmine.lighttpd.net/issues/729> perl v5.14.2 2011-02-27 Plack::Middleware::LighttpdScriptNameFix(3pm)