behaviour when client drops the connection?
rob.halff at gmail.com
Wed Sep 2 09:15:22 CEST 2009
Stuart, pages taking 1 hour to load is an application design problem.
You should use http to show results not to trigger a one hour request
and let the user/client wait for it.
You could generate a code instantly to confirm the request is being processed.
And let the client check, using this code, whether the request is done
every minute or whatever time interval you choose.
If the request is not based on user parameters, you could use cron to
generate the result page.
2009/9/2 Rogério Schneider <stockrt at gmail.com>:
> Stuart, I think 60 minutes is too much time even for Varnish to wait.
> In default configuration Varnish would wait only for, if I remember, 60
> seconds and then give up on that request.
> This can be tuned with -p params, like "first_byte_timeout". You can read
> more here:
> Best Regards,
> On Sun, Aug 30, 2009 at 10:11 PM, stuart yeates <stuart.yeates at vuw.ac.nz>
>> I'm looking to use varnish in front of an XSLT/PostgreSQL/Tomcat/Java
>> site and have a question about varnish's behaviour when a client drops a
>> The problem is that there are a relatively small number of pages which
>> are _very_ slow to generate (>60 minutes) and a large number that are
>> relatively fast. Clients tend to abort the slow pages, so (using our
>> current reverse proxy) they never make it into the cache.
>> Ideally I'd like to make varnish continue the request and cache the
>> result. Is that possible?
>> Is there a way to make these slow-to-generate pages have a much longer
>> Stuart Yeates
>> http://www.nzetc.org/ New Zealand Electronic Text Centre
>> http://researcharchive.vuw.ac.nz/ Institutional Repository
>> varnish-misc mailing list
>> varnish-misc at projects.linpro.no
> Rogério Schneider
> MSN: stockrt at hotmail.com
> GTalk: stockrt at gmail.com
> TerraVoip: stockrt
> Skype: stockrt
> varnish-dev mailing list
> varnish-dev at projects.linpro.no
More information about the varnish-dev