Re: [squid-users] 2nd recv delay on GET

This is not symptoms I recognize.

Please make a packet dump of the traffic both between your client and
Squid and between Squid and the web server when processing this request.

Regards
Henrik

tis 2003-04-01 klockan 21.24 skrev David Rosenbloom:
> With the default squid config with Basic auth enabled, I am experiencing
> the following:
>
> In my app which sends HTTP requests, a loop processes recv()'s until a 0
> or error return. With direct connect and via a socks proxy (dante), this
> works fine, but with squid, the 2nd recv (rather, all recvs after the
> initial) takes a _long_ time before returning. The data is (eventually)
> received complete, but the waits are a problem.
>
> The headers passed in with the call are
> Pragma: no-cache
> Proxy-Connection: Keep-Alive
> Proxy-Authorization: Basic" : [creds]
>
> The HTTPS calls which use CONNECT do not exhibit this problem.
>
> Is there something - header, socket option - on the calling end that can
> address this? On the squid config end?
>
> thanks,
> - davidr
>

-- 
Free Squid-users support provided by Henrik Nordström <hno@squid-cache.org>
PayPal donations welcome if you consider my Free Squid support helpful.
https://www.paypal.com/xclick/business=hno%40squid-cache.org&cn=Comment
If you need commercial Squid support or cost effective Squid and
firewall appliances please refer to MARA Systems AB, Sweden
http://www.marasystems.com/, info@marasystems.com