Bug ID 625376: In some cases, download of PAC file by edge client may fail

Last Modified: Sep 13, 2023

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

Known Affected Versions:
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, 11.5.3 HF2, 11.5.4 HF1, 11.5.4 HF2, 11.6.0, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2

Fixed In:
13.0.0, 11.6.1 HF2, 11.5.4 HF3

Opened: Oct 27, 2016

Severity: 3-Major

Related Article: K03229274

Symptoms

Edge client may fail to download PAC file and incorrectly apply proxy configuration after VPN connection.

Impact

PAC file download will fail and client will use incorrect proxy settings due to unavailability of PAC file.

Conditions

- User machine proxy configuration points to a proxy auto configuration file. - Network access proxy configuration points to a proxy auto configuration file. - PAC file URI in either case has uppercase characters. - PAC file is hosted on a server where resource names are case sensitive.

Workaround

Use only lowercase characters in PAC file URI.

Fix Information

Now Edge client can download PAC files from URIs that have uppercase as well as lowercase characters.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips