Bug ID 676026: Add support for more profiles with the http-transparent profile.

Last Modified: Nov 07, 2022

Bug Tracker

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

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3,,,,,,,, 12.1.4,, 12.1.5,,,, 12.1.6, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,,,, 13.1.4,, 13.1.5,, 14.0.0,,,,,, 14.0.1,

Fixed In:

Opened: Jul 28, 2017
Severity: 4-Minor


Some profiles were prevented from being configured on a virtual server together with the http-transparent profile when they were not incompatible.


The affected profiles could not be used together with http-transparent.


The http-transparent profile is attached to a virtual, and the following profiles are attempted to be used on the same virtual: clientssl, serverssl, oneconnect, http-security (psm).



Fix Information

The validation for the http-transparent profile is more lenient. It will allow additional profiles on the same virtual server that were previously prevented.

Behavior Change

Extra profiles are now allowed to be configured on a virtual server with a http-transparent profile. These include: clientssl, serverssl, oneconnect, and http security (psm) profiles. Previously, the addition of these profiles would be disallowed via validation.