Bug ID 995413: WinInet caches the IP address of hostnames accessed while traversing access policy in Edge Client for around 25 minutes.

Last Modified: Apr 28, 2025

Affected Product(s):
APM-Clients TMOS(all modules)

Fixed In:
7.2.2

Opened: Feb 19, 2021

Severity: 3-Major

Symptoms

- Edge Client connects to old cached IP address of one/many of the hostnames encountered during access policy. - In locked mode Edge Client, authentication in access policy may get stuck and user may see blank page in browser control.

Impact

- Edge Client connects to old cached IP address of one/many of the hostnames encountered during access policy. If old IP address is not the valid address, authentication may fail or be stuck and user may see blank page in browser control. - Locked mode Edge Client may be stuck on during authentication and user may see blank page in browser control.

Conditions

- Authentication/access policy encounters hostnames which have changing IP addresses. - Edge Client has processed the access policy and connected to VPN once and the subsequent attempt happens in 25 minutes in the same instance of Edge Client. - Old IP address is cached by Edge Client for one of the hostnames and the IP address for the said hostname has changed. - In case of Locked mode client, Stonewall service does not have exception for old IP address anymore.

Workaround

None

Fix Information

Authentication happens in a separate process due to the fix and old IP address is not cached by WinInet in Edge Client process.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips