MyAnswerDialer(this, &PeerPoolMgr::handleSecuredPeer));
const int peerTimeout = peer->connect_timeout > 0 ?
- peer->connect_timeout : Config.Timeout.peer_connect;
+ peer->connect_timeout : Config.Timeout.peer_connect;
const int timeUsed = squid_curtime - params.conn->startTime();
// Use positive timeout when less than one second is left for conn.
const int timeLeft = max(1, (peerTimeout - timeUsed));
* establishment timeout and close the connection on timeouts. This is probably
* better than having dedicated (or none at all!) timeouts for peer selection,
* DNS lookup, TCP handshake, SSL handshake, etc. Some steps may have their
- * own timeout, but not all steps should be forced to have theirs.
+ * own timeout, but not all steps should be forced to have theirs.
* XXX: tunnel.cc and probably other subsystems does not have an "overall
* connection establishment" timeout. We need to change their code so that they
* start monitoring earlier and close on timeouts. This change may need to be
/// Sets the read timeout to avoid getting stuck while reading from a
/// silent server
- void setReadTimeout();
+ void setReadTimeout();
void initializeSsl(); ///< Initializes SSL state