Bug ID 461597: MAC edge client doesn't follow HTTP 302 redirect if new site has untrusted self-signed certificate

Last Modified: Oct 07, 2023

Affected Product(s):
BIG-IP APM(all modules)

Known Affected Versions:
11.5.1 HF1, 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.1 HF10, 11.5.1 HF11, 11.5.2 HF1, 11.5.3 HF1, 12.1.0 HF1, 12.1.0 HF2, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2

Fixed In:
12.0.0, 11.6.0 HF5, 11.6.0, 11.5.3 HF2, 11.5.3

Opened: May 09, 2014

Severity: 4-Minor

Symptoms

BIG-IP Edge Client for Mac does not follow HTTP 302 redirect if new site has an untrusted self-signed certificate.

Impact

User might not be able to log in if HTTP 302 redirect is configured for a site with an untrusted certificate.

Conditions

BIG-IP Edge Gateway and Mac Edge Client and HTTP 302 redirect to new site with untrusted certificate

Workaround

Configure APM with trusted certificate or configure client machine to trust APM's certificate

Fix Information

BIG-IP Edge Client for Mac now follows HTTP 302 redirect if the new site has an untrusted self-signed certificate and the user will be able to log in successfully.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips