I am using version 1.59 of perlbal from CPAN with slight modification to /usr/bin/perlbal (unofficial drop privileges patch from David).<br>Thanx,<br>HB<br><br><br><div><span class="gmail_quote">On 9/16/07, <b class="gmail_sendername">
Hemant Bist</b> <<a href="mailto:hemant_bist@yahoo.com">hemant_bist@yahoo.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi, I have perlbal running in reverse proxy role. I have a case, where the backend mod_perl servers redirect the the perlbal (via X-REPROXY-URL header) to a server that takes around 2 min to serve all the<br>data to the browser. I am consistenly getting timeout in less than min in such case.
<br><br><br>Changing the max_idle_time in ClientHTTPBase.pm to return 180 seems to fix the problem for me. (But I am not sure if it also increases the timeout for the persistent browser connections to 180 sec)<br><br>Is this a known bug/behaviour. Or something that I only I am noticing.
<br><br>I see a patch from Justin to configure the timeout per service in this list(<a href="http://lists.danga.com/pipermail/perlbal/2007-June/000518.html" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://lists.danga.com/pipermail/perlbal/2007-June/000518.html</a>
).<br> Is it to workaround this bug?<br><br>Thanx,<br><span class="sg">HB<br><br><br><br>
</span></blockquote></div><br>