From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 419] New: Bump lighttpd package to 1.4.23
Date: Tue, 23 Jun 2009 16:25:41 +0000 (UTC) [thread overview]
Message-ID: <bug-419-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=419
Host: i686-linux
Target: arm-softfloat-linux-uclibcgnueabi
Summary: Bump lighttpd package to 1.4.23
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: enhancement
Priority: P5
Component: Outdated package
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: gustavo at zacarias.com.ar
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Created an attachment (id=421)
--> (https://bugs.busybox.net/attachment.cgi?id=421)
Bump lighttpd package to 1.4.23
lighttpd 1.4.23 is out, there are many bugfixes from 1.4.20 currently in
buildroot:
* Fix workaround for incorrect path info/scriptname if fastcgi prefix is
?/? (fixes #729)
* Finally removed spawn-fcgi
* Fix bug with FastCGI request id overflow under high load; just use always id
1 as we don?t use multiplexing. (thx jgray)
* Workaround broken operating systems: check for trailing ?/? in filenames
(fixes #1989)
Plus fixes from 1.4.22 and 1.4.21.
spawn-fcgi was included up to version 1.4.22 and is now a separate project,
there's a new package in bug #417 to include this functionality once again.
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2009-06-23 16:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-23 16:25 bugzilla at busybox.net [this message]
2009-07-01 13:33 ` [Buildroot] [Bug 419] Bump lighttpd package to 1.4.23 bugzilla at busybox.net
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-419-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.