[Gllug] Lighttpd deciding that 404 is for ever and ever

[Aaron Trevena]

Hi All,

I'm adding lighttpd a load balancing reverse proxy (perlbal) and some
mod_perl backends to act as a http cache / accelorator (with mod_cache
and modproxy), and finding that it decides that 404 and 500 status
should remain so for ever, regardless of what the backend returns a
second, hour or millenium later.

Anybody else found this issue - or more importantly know a work around or fix.

Failing that - are there any fast, lightweight and sane http
accelerators worth trying?

lighttpd is starting to annoy me and Varnish is a bit eccentric /
experimental (and makes danga-ware documentation look like the library
of alexandria).

A.

-- 
http://www.aarontrevena.co.uk
LAMP System Integration, Development and Hosting
-- 
Gllug mailing list  -  Gllug at gllug.org.uk
http://lists.gllug.org.uk/mailman/listinfo/gllug