lighty's life: PRE-RELEASE: lighttpd-1.5.0-r1605.tar.gz

PRE-RELEASE: lighttpd-1.5.0-r1605.tar.gz

jan — Sat, 03 Feb 2007 22:50:00 +0000

A lot of changes made it into the svn recently. It is time again to spread the code to more testers than just the few early adaptors who are using the svn-trunk/

Please try out the new stuff around async-io and dynamic compression of content. Even directory-listings are now automaticly compressed. Just load mod_deflate and set

deflate.mimetypes = ( "text/html" )

Download:

updated lighttpd-1.5.0-r1605.tar.gz

ChangeLog (r1605):

added check for leading slashes in mod_rewrite
improved async-io performance for files between 4k and 16k
fixed compression of static files in mod_deflate
fixed configure check for the library providing aio_read()
fixed moddirlisting, modstaticfile and the internal error-pages for mod_deflate
fixed compilation on FreeBSD and MacOS X

ChangeLog (r1593):

added O_NOATIME support to the network-backends linux-sendfile and writev
added a portable, threaded network-backend based on glib’s gthread
added threaded stat()
added url.redirect-code to mod_redirect to set other HTTP status-codes than 302
added filter-API and mod_chunked and mod_deflate for dynamic compression
added a static balancer for mod-proxy-core
added $HTTP[“request-method”] and $PHYSICAL[“path”] conditionals
fixed X-Sendfile support in mod-proxy-core
fixed crash if mtime is 0
added cmake as experimental build-system
fixed urls in AJP13-protocol of mod-proxy-core
added support for “now” and “weeks” to mod-expire
added mod-magnet

"PRE-RELEASE: lighttpd-1.5.0-r1605.tar.gz" by Hank

Sat, 17 Feb 2007 23:14:12 +0000

Can someone verify that setenv.add-environment works in the latest release? I'm using this and it does not pass the env variable to php. This is my basic config
server.modules += ( "mod_proxy_core")
server.modules += ( "mod_proxy_backend_fastcgi" )
server.modules += ( "mod_setenv")
$HTTP["url"] =~ "\.php$" {
proxy-core.balancer = "round-robin"
proxy-core.protocol = "fastcgi"
proxy-core.check-local = "enable"
proxy-core.backends = ( "unix:/tmp/php-fastcgi.sock" )
setenv.add-environment = ("testenv" => "fooabcd")
}

"PRE-RELEASE: lighttpd-1.5.0-r1605.tar.gz" by Imran

Sat, 17 Feb 2007 09:42:19 +0000

I have built this on three different CentOS 4.4 systems with PCRE + LibAIO installed. The system builds fine, but it does not build mod_cgi. Has anyone else come across this issue ? I tried to see if I need to manually enale this, but I could not do so. Anyone know why this might be the case ? Note: my configure line is : ./configure --prefix=/usr/local/lighttpd15 --with-linux-aio

"PRE-RELEASE: lighttpd-1.5.0-r1605.tar.gz" by Son Nguyen

Thu, 15 Feb 2007 21:46:39 +0000

I looked at the benchmark post for async-io and it's amazing, look forward to 1.5 stable release. Thanks all developers & testers

"PRE-RELEASE: lighttpd-1.5.0-r1605.tar.gz" by Michael

Thu, 15 Feb 2007 15:24:06 +0000

I can`t compile mod_geoip.c ! More errors after `make`. Pls, can you integrate this module in new release?

"PRE-RELEASE: lighttpd-1.5.0-r1605.tar.gz" by Sam

Mon, 12 Feb 2007 09:03:45 +0000

Anyone has a working sample config file? i am a little confused at the new syntax. I am trying to turn on webdav, cgi and mod upload progress to test.

"PRE-RELEASE: lighttpd-1.5.0-r1605.tar.gz" by duck

Thu, 08 Feb 2007 20:49:39 +0000

Compiles and work good. But doesn't pass index-files to fcgi.

"PRE-RELEASE: lighttpd-1.5.0-r1605.tar.gz" by Sam

Wed, 07 Feb 2007 12:25:02 +0000

my bad...the '__ctype_b_loc' error is due to wrong libc library.

"PRE-RELEASE: lighttpd-1.5.0-r1605.tar.gz" by Sam

Wed, 07 Feb 2007 09:19:27 +0000

hi, jan: i took the long path. compiled glib-2.0 together with uclibc. got past the gthread and glib checking. successful make. thanks much! i just tried starting in, but got error: can't resolve symbol '__ctype_b_loc'. got to investigate further....

"PRE-RELEASE: lighttpd-1.5.0-r1605.tar.gz" by David Weekly

Tue, 06 Feb 2007 09:33:00 +0000

Neato! So glad to see this release coming together. I took a peek and didn't seem to see use of TCP_DEFER_ACCEPT to delay accept() processing until the first packet of data from the client arrives (performance boost!) or TCP_QUICKACK to disable the sending of an extra ack to the client request when the server header is soon to print (reduce packet transmission rate). Any plans for these?

"PRE-RELEASE: lighttpd-1.5.0-r1605.tar.gz" by Jan Kneschke

Tue, 06 Feb 2007 09:22:12 +0000

lighttpd compiles without gthread-2.0 (after adjusting the configure script), but not without glib-2.0. Linking against a static glib-2.0 should be all you need when you build for uclibc.

"PRE-RELEASE: lighttpd-1.5.0-r1605.tar.gz" by Sam

Tue, 06 Feb 2007 08:28:25 +0000

is there a switch to disable gthread? i need to compile this for uclibc.

"PRE-RELEASE: lighttpd-1.5.0-r1605.tar.gz" by Jan Kneschke

Sun, 04 Feb 2007 22:34:09 +0000

frank, this is fixed in SVN now.

"PRE-RELEASE: lighttpd-1.5.0-r1605.tar.gz" by Frank

Sun, 04 Feb 2007 14:13:18 +0000

mod_deflate doesnot work quite right. OS: Fedora Core 6 I see following in error logfile 2007-02-04 22:09:11: (/home/fang/build/build/lighttpd/src/mod_deflate.c.786) file was shrinked: /mnt/linux/WebDev/htdocs/misc/j11.html 2007-02-04 22:09:11: (/home/fang/build/build/lighttpd/src/mod_deflate.c.1002) compress file chunk failed. /home/fang/build/build/lighttpd/src/connections.c.1299: (trace) (error) /home/fang/build/build/lighttpd/src/connections.c.820: (error) I thought only WRITE_RESPONSE_* need fdevent-out

"PRE-RELEASE: lighttpd-1.5.0-r1605.tar.gz" by tibco

Sun, 04 Feb 2007 04:30:39 +0000

for me, 1.can not show 404 error 2.can not list dir when I tried to do those, browser hung. curl show me 301 rolled back to 1524, problems gone.

"PRE-RELEASE: lighttpd-1.5.0-r1605.tar.gz" by Scott MacVicar

Sun, 04 Feb 2007 01:29:52 +0000

Running on our development servers now without any problem. Only change was adding mod_proxy_backend_fastcgi to the list of loaded modules. I've still got an issue with FastCGI not handling loading of the directory index document, in most cases index.php. Works fine if the URI explicitly contains the filename, possibly a configuration issue on our end.