This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

WAF never detects when real webserver is offline

Maybe I'm confused about how this is supposed to work? I have two real webservers behind a virtual server. If I turn one off (totally off, not pingable), The real webserver light stays green next to that server. The virtual webserver then becomes unreachable. The virtual webserver should stop forwarding requests to the offline real webserver shouldn't it? This is on 9.203-3. Thanks, Doug

This thread was automatically locked due to age.

0 BarryG over 10 years ago

Hi,

See https://community.sophos.com/products/unified-threat-management/astaroorg/f/51/t/22364

You may want to add a feature request and/or talk to your reseller.
UTM (Formerly ASG) Feature Requests: Hot (1827 ideas)

Barry
Cancel
Vote Up 0 Vote Down

Cancel
0 Evianne over 10 years ago in reply to BarryG

Hi,

I can not reproduce your issue. I tested it with v9.205 and it works fine. Sometimes, the view in Webadmin only change with a reload.

If the web server is unreachable, the logs shows the following:
[proxy_http:error] (...) AH01114: HTTP: failed to make connection to backend: (...)

Best,
Sabine
Cancel
Vote Up 0 Vote Down

Cancel
0 thedukeness over 10 years ago

I figured it out once I updated to 9.205-12. It was just that the failover timeout in 9.203-3 was 5 minutes. In this new version you can customize it. I never had any real webservers down for longer than 5 minutes so WAF never set the status to down. Thanks all for checking it out.
Cancel
Vote Up 0 Vote Down

Cancel