This problem seems to be caused by Cisco’s Anomaly Guard Module (AGM), which sits on the network between clients and servers and attempts to authenticate clients by challenging them with an HTML meta refresh. There isn’t much you can do about it, short of asking your server network provider to disable basic protection for HTTP on their AGM.
This problem seems to be caused by Cisco’s Anomaly Guard Module (AGM), which sits on the network between clients and servers and attempts to authenticate clients by challenging them with an HTML meta refresh. Contact your network provider and ask them to disable basic protection for HTTP.
