Bug ID 440263: HTTP profile gets set to http-transparent by ASM deployment wizard

Last Modified: Oct 06, 2020

Bug Tracker

Affected Product:  See more info
BIG-IP ASM(all modules)

Known Affected Versions:
11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.10, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9

Fixed In:
11.6.0

Opened: Dec 10, 2013
Severity: 3-Major

Symptoms

If the default HTTP profile "http" was modified, when creating a new virtual server in the ASM deployment wizard, the associated HTTP profile is "http-transparent".

Impact

HTTP profile gets set to the wrong profile. This makes the PEM deployment unusable, updating the security policy will return an error "01070734:3: Configuration error: In Virtual Server (/Common/test) HTTP is configured as a Transparent Proxy, and thus is incompatible with any other filter other than PEM."

Conditions

This will occur if you have modified the default http profile and then create a new virtual server using the ASM deployment wizard.

Workaround

After using the wizard, you can set the http profile for the virtual server back to http

Fix Information

If you create a security policy using the deployment wizard, the associated HTTP profile is "http".

Behavior Change