Forum Discussion
Asm policy blocking
The reason is that you must know if your application uses secure HTTP (that's what the "s" means in HTTPS) or unsecured HTTP for data transmission. Most applications today use HTTPS. Security is provided to data in transit by encrypting the payload using TLS (SSL). ASM cannot apply security processing to encrypted data. This data must be unencrypted first. To do that, you need to allow BIG-IP to handle the unencryption before it reaches the security policy. Here is a good explanation about the server vs. client SSL profiles which will facilitate this:
https://support.f5.com/csp/article/K72355246
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com