Sorry for the private answer, Rogério. 2009/10/9 Rogério Schneider <[email protected]>: >> I deployed varnish on a webserver that also runs PHP to serve larger >> files of up to about 1GB. NOTE, I am using the stock varnish shipped >> with Debian 5, which is varnish version 1.1.2. > > We (everyone agrees, right?) recommend using a newer one :)
That would be best, of course. :) But varnish isn't core business for me, so I'm relying on distributions to keep this updated/secure. >> Is there a time limit like this in newer versions of varnish? Is there >> a workaround I can use? It seems "pass"ing these requests doesn't >> help, but "pipe"ing them appears to help. Is there a better solution >> than hardcoding "pipe"s of all requests that could take more than 10 >> minutes? > > Take a look at the startup option: "send_timeout" > > http://varnish.projects.linpro.no/browser/tags/varnish-1.1.2/bin/varnishd/mgt_param.c Thanks. The way I read this option, it is intended to take care of the situation where the client isn't receiving data. However, I have confirmed that send_timeout was in fact guilty as charged, by setting it to 300 seconds and observing that the connection was closed after 5 minutes instead of 10. Is this fixed in varnish 2.0.4? Looked at this page: http://varnish.projects.linpro.no/browser/tags/varnish-2.0.4/varnish-cache/bin/varnishd/mgt_param.c and I'm not any wiser yet. :-) Regards, Ketil _______________________________________________ varnish-misc mailing list [email protected] http://projects.linpro.no/mailman/listinfo/varnish-misc
