Forum Discussion
Stanislas_Piro2
Dec 08, 2017Cumulonimbus
I can understand why CLIENT_ACCEPTED is triggered but why HTTP_REQUEST? And why using only matching at TCP connection in LTP causes LTP parameter requires { http tcp } have http included?
I had the same strange behavior... LTP is a feature to replace HTTP-CLASS in versions before 13.0.
In version 11.X, we could select manually policy requirements, since version 12.0, this is done automatically and some requirements are wrong:
- http is always enabled
- when we want to add a condition on SSL sever name, it requires ssl-persistence and not clientssl...