Hi all, I've found an issue with the devel version of webpy with fastcgi through flup on a lighttpd backend. It appears to be related to this:
http://groups.google.com/group/webpy/browse_thread/thread/4cda6f36f63319d1/96bec960fa289c29?lnk=gst&q=flup+socket.error#96bec960fa289c29 The issue is that web.seeothers somehow mess with the socket writing, and I get a 5 second timeout on a redirect, instead of an immediate response. I can reproduce the issue using the code below (pretty much the simplest setup possible). Unfortunately, you need to run it through lighttpd in fastcgi mode -- it won't appear if just run using the internal server. http://pastebin.com/m1228e3e4 I initially found the problem with the .5 version of flup -- thought that was the issue, so I upgraded. Still happens. In the error.log for lighttpd, I get: 2008-03-24 00:30:31: (mod_fastcgi.c.1739) connect failed: Connection refused on unix:/tmp/fastcgi1.socket-0 2008-03-24 00:30:31: (mod_fastcgi.c.2851) backend died, we disable it for a 5 seconds and send the request to another backend instead: reconnects: 0 load: 1 Anand: any idea what might be causing this? I noticed the redirects got an overhaul in the .3 version. Thanks, Justin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web.py" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/webpy?hl=en -~----------~----~----~----~------~----~------~--~---
