-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday 30 July 2003 04.32, Allan Liska wrote:
> I have a user behind a Squid proxy who is receiving a browser > timeout error when initiating a particularly large database query. > The query takes almost 2 minutes to complete, and it does complete > without a problem if he bypasses the Squid box, but when he goes > through the Squid box the browser returns the cached objects, and > no database data. What is seen in access.log? > Looking through the documentation it appears there may be two ways > to resolve this problem. The first is to create an always direct > access list for the remote site and have the user just pass through > the Squid box with no proxying. This is not what the always_direct directive does. The always_direct directive tells Squid that Squid must go direct to the source when forwarding the request, not using any cache peers. It does NOT control caching or what requests the browsers send to Squid. > The second is to increase one of the timeout values, this is where > I am a little confused. Which timeout value would I need to > increase? At first glance the variable I want to change seems to be > connect_timeout, but is there a better timeout variable to adjust > in this case? If the request only takes a couple of minutes to complete the default timeouts should be fine, unless ofcourse you have tuned them down. The relevant timeouts are in order read_timeout client_lifetime then there also is the following slightly realated timeouts, but from your description these are not relevant request_timeout persistent_request_timeout pconn_timeout Regards Henrik - -- Donations welcome if you consider my Free Squid support helpful. https://www.paypal.com/xclick/business=hno%40squid-cache.org If you need commercial Squid support or cost effective Squid or firewall appliances please refer to MARA Systems AB, Sweden http://www.marasystems.com/, [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE/J21s7oQzBsSTDmURAmtjAKCu9fcS4mgPJxyn/e2UGyPJ5epeFACdF8DC xPr0Ye4rbocIv+dZBCMHNaM= =ccKr -----END PGP SIGNATURE-----
