lighty labs

2009-08-01

08:44 Lighttpd Bug #2046 (Obsolete): use HANDLER_GO_ON for mod_proxy_core and 504 errors

In my opinion the 504 should be handled by the http-state machine in connections.c .
The patch bellow changes all HA... e-razor

2009-07-28

15:04 Lighttpd Development: RE: PATCH: allow server.error-handler-504

Yeah, we've had a more or less rational discussion about this at the IRC channel.
I agree about the problem with s... e-razor

2009-07-06

14:09 Lighttpd Support: RE: mod_proxy_core and HTTP timeouts (no HTTP response)

Ok, i guess it's a bug in lighttpd, and fixed it. e-razor

09:33 Lighttpd Development: [1.5] PATCH: allow server.error-handler-504

Hi all,
this generates a redirect (via Location: ...) for error 504 (protocol timeout in mod_proxy_core).
Cheer... e-razor

09:30 Lighttpd Development: [1.5] PATCH: added 2 settings for mod_proxy_core (max-backlog-size & host-disable-time)

Hi there,
the patch bellow adds two new settings for mod_proxy_core:
* max-backlog-size
For HTTP- proxying you... e-razor

09:23 Lighttpd Development: [1.5] PATCH: use HANDLER_GO_ON for mod_proxy_core and 504 errors

Hi all,
in my opinion the 504 should be handled by the http-state machine in connections.c .
The patch bellow c... e-razor

2009-07-03

08:31 Lighttpd Support: mod_proxy_core and HTTP timeouts (no HTTP response)

Hi all,
i got some problems with mod_proxy_core of the latest svn.
My setup looks like this:... e-razor