12-14-2015 05:22 AM - edited 03-12-2019 06:09 PM
Hi all,
We are seeing the following syslog massages when we are trying to authenticate via the ASA:
Non-HTTP connection from outside:10.100.100.1/51253 to inside:192.168.76.13/8905 denied by redirect filter; only HTTP connections are supported for redirection.
Built inbound TCP connection 5181 for outside:10.100.100.1/51253 (10.100.100.1/51253)(LOCAL\testuser) to inside:192.168.76.13/8443 (192.168.76.13/8905) (testuser)
Teardown TCP connection 5181 for outside:10.100.100.1/51253(LOCAL\testuser) to inside:192.168.76.13/8443 duration 0:00:00 bytes 0 Flow closed by inspection (testuser)
Is there any workaround the above mentioned issue?
Thanks in advance,
Dave.
Solved! Go to Solution.
12-14-2015 09:44 AM
Hello;
Explanation For the CoA feature, the redirect ACL filter drops the matching non-HTTP traffic during the redirect processing
Recommended Action Validate the redirect ACL configuration on the ASA. Make sure that the correct filter is used to match the traffic to redirect and does not block the flow that is intended to be allowed through.
http://www.cisco.com/c/en/us/td/docs/security/asa/syslog-guide/syslogs/logmsgs1.html#pgfId-8070351
Seems like there is a misconfiguration in CoA.
Mike.
12-14-2015 09:44 AM
Hello;
Explanation For the CoA feature, the redirect ACL filter drops the matching non-HTTP traffic during the redirect processing
Recommended Action Validate the redirect ACL configuration on the ASA. Make sure that the correct filter is used to match the traffic to redirect and does not block the flow that is intended to be allowed through.
http://www.cisco.com/c/en/us/td/docs/security/asa/syslog-guide/syslogs/logmsgs1.html#pgfId-8070351
Seems like there is a misconfiguration in CoA.
Mike.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide