ASM policy in transparent mode causes corrupt web page

I have a ASM policy configured in Transparent mode. When it is turned on, the web page does not behave correctly, and using a HTML capture, the HTML is longer (or actually has more calls to the webserver). Turning the policy off of the Virtual Machine, the web page behaves as expected. Creating a new policy for the VM and the web page behaves as expected. Could the original policy be corrupt? It worked for a year until a recent code deploy. Creating a templet from the original policy and then a policy off of that, the behavor is the same as the original policy.

I just wonder if the application language is different? Just a thought really.

are you using any asm feature which injects script to client?

if yes, can you try to turn it off?

are you using any asm feature which injects script to client?

if yes, can you try to turn it off?

Nope. It was a generic policy. No irules or injects.

Nope. It was a generic policy. No irules or injects.

you are not using feature such as web scraping, csrf, etc, are you?

you are not using feature such as web scraping, csrf, etc, are you?

No. The code is all coming from Websphere. HTML and Java script.

No. The code is all coming from Websphere. HTML and Java script.

Not an answer but i would probably export both policies in XML format and take a look at them both side by side to see if anything odd/spurious exists on the faulty policy.

Not an answer but i would probably export both policies in XML format and take a look at them both side by side to see if anything odd/spurious exists on the faulty policy.

F5 support found the problem. Chunking with ASM. And Data Guard was masking fileds it thought were credit cards… Thanks Support!