I guess I'm looking for a way for the Squid server to check that port 80 and 443 are being accepted. If for some reason they are not, I'd like traffic to just be forwarded to the backend server. What ways could this be done?
-----Original Message----- From: Chris Perreault [mailto:[EMAIL PROTECTED] Sent: Monday, September 13, 2004 12:04 PM To: Brad Taylor Cc: [EMAIL PROTECTED] Subject: RE: [squid-users] Bypass Squid -----Original Message----- From: Brad Taylor [mailto:[EMAIL PROTECTED] Sent: Monday, September 13, 2004 11:08 AM To: Henrik Nordstrom Cc: [EMAIL PROTECTED] Subject: RE: [squid-users] Bypass Squid I'm wondering how I could redirect the client request to the back end server if Squid stopped working for some reason. This would be while squid was in reverse proxy mode and we would not have access to the clients. Any thoughts on if this could be done? ~~~~~~~~~~~~~~~~` ~~~~~~~~~~~~~~~~~ A public DNS record has an entry saying 12.12.12.12 is what yoursite.com resolves to. Squid (at 12.12.12.12) is saying traffic coming in to yoursite.com should really go to 10.10.10.10, on your back-end network. Squid goes down and it is just like your webserver goes down. What happens if your webserver goes down and your clients don't have access to it? Ie: your webserver is critical, so there are two of them, for redundancy/failover. If your webserver is that critical, then your infrastructure to it should be just as redundant so you don't have a single point of failure. In that case, having two squid boxes set up for failover would do the trick. OR...call the person who manages DNS for you and have them change the IP address to wherever your website can be reached. OR..unplug squid and let traffic through to the back end webserver...although it would be more secure to move the webserver to wherever squid sits and give it the 12.12.12.12. ip address. In a nutshell, everyone thinks your proxy is your webserver. If it goes down people will still try to reach it. Chris
