[squid-users] Q: http keepalives and time_wait sockets

Q1: Reading the archives of this mailing list, I concluded that squid does not support using keep-alive in connections to source servers.

I assume that setting keep-alive On on an Apache source server cached by squid would thus be harmless: since squid does not do keepalives, the connections would
be terminated immediately - Apache would waste time keeping processes busy waiting on sockets after squid terminated its http/1.0 request.

The advantage being that is the same apache server serves some other site beside the one cached by squid, or if squid is disabled temporarily, keepalives will
be automatically in effect.

Is this correct? Are there any advantages/drawbacks that are escaping me?

Q2: Using squid as reverse proxy, I have seen that a lot of sockets (200 to 300) are always listed on the origin server, coming from the squid server, in
TIME_WAIT status.
Using netstat on the squid server itself at the same time, I see about 10 open sockets, none of which in TIME_WAIT.
Is this normal? Is it a sign of some misconfiguration? (note: there is probably a firewall currently sitting between the two servers). Can it be related somehow
to keepalives?

Thanks
gaetano
Received on Mon Apr 19 2010 - 13:41:18 MDT