Forum Discussion
bowlingbe
Nimbostratus
Dec 15, 2012Internal Sites not Working through local APM proxy http://127.0.0.1:44777/
We are seeing an issue where internal sites are not working when connecting through the f5 APM edge device. We have noticed the the virutal adapter sets the proxy to us an automatic configuration scr...
bowlingbe
Nimbostratus
Jan 16, 2013The 127. pac file is the correct file. I'm not sure how group policy would do that. We have policies in place that do set the correct proxy.pac file in IE. The issue is that APM creates it's own adapter and downloads the file locally and points VPN users to the 127. I just want the VPN adapter to use the same path as the normal IE settings.
kimhenriksen
Cirrocumulus
Apr 05, 2017I know this is an old thread but.. did you make any progress with this? We´re trying to do the same here, we dont want to use the 127.0.0.1 url for the proxyscript. We want the proxy.fakenet.net/proxy.js
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects