Thanks, Alex. I do have some concerns that 'reconfigure' may cause disruptions in certain situations, but I haven't seen it yet.
Perhaps it is most likely to cause problems when connections are first being established, or when they are changing states. It seems to do a good job of not disrupting established WebSocket connections. One other idea I had was to use 'iptables' to prevent new TCP connections to port 443 as the first phase of shutdown. I think that would probably work, and would not have the potential bad behavior of 'reconfigure'. For my 'reconfigure', I'm simply commenting out the https_port line which causes Squid to listen on 443. Thanks again. _______________________________________________ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users
