Applies To:Show Versions
- 12.1.0, 11.6.1, 11.5.4, 11.5.3, 11.5.2, 11.5.1, 11.2.1
In May 2016, Apple posted the release of the iOS Edge Client version 2.0.8. Users should download this new version from the app store.
- Features and enhancements in 2.0.8
- Behavior changes in 2.0.8
- Known issues with iOS affecting Edge Client 2.0.8
- Fixes in 2.0.8
- Legal notices
- Contacting F5 Networks
Features and enhancements in 2.0.8
|548472||iOS Edge Client 2.0.8 now supports client side server name indication (SNI).|
Known issues with iOS affecting Edge Client 2.0.8
The following are known iOS issues that affect the user experience when Edge Client is used on an iOS device. These issues may be addressed in the future by Apple.
|476958||If a fully qualified host is specified in the proxy bypass list, users navigating to the host using the short form make use of the proxy in iOS 7, but this bypasses the proxy on iOS 8. iOS 8 takes into account the DNS suffix for proxy bypass.|
|518576||After users trigger VPN On Demand, Safari displays the following error message, Safari could not open the page because the server stopped responding. Users fail to reach the internal resource until they refresh the web page. This only occurs when users try to reach a domain that ends in ".local."|
|557905||On iOS 9, if an managed app is being updated while Per-App VPN is active, the updated app might not make use of the active session until the active session is expired and a new one is created. As a workaround, wait until the current session expires, and restart the updated app.|
|559388||After users upgrade Edge Client to a later version (such as 2.0.7) on iOS 9, the following message might be displayed when launching applications that trigger VPN On Demand (including per-app VPN): Please launch Edge Client to enable the VPN connection. To address this issue, users, when prompted, should manually launch Edge Client to accept the use of VPN. VPN On Demand connections are not available unless users accept the use of VPN in Edge Client.|
|582315||If users first establish a VPN connection using VPN on-demand, the connection fails when the proxy is required to access the backend server. This happens when users enable proxy configuration in the network access resource, located on the server side, and the VPN configuration has VPN on-demand suffixes on the client side. To work around this issue, reestablish the connection by refreshing the webpage in Safari.|
|588205||When the iOS device goes into sleep mode, the on-demand connection terminates before the disconnect timeout. This can cause the iOS system to go into a non-recoverable state, disconnecting the VPN. In this state, Edge Client cannot reconnect, even when within the disconnect timeout limit.|
|591017||On iOS 9 with "Connect on Demand" enabled for a VPN configuration, the system downloads the proxy auto-config (PAC) file only after a delay. Users should wait for more than one minute after establishing the VPN tunnel so the PAC script downloads and applies.|
|591501||On iOS 9, when per-app VPN is triggered by Safari, the session is deleted after an inactivity timeout, instead of after the expected on-demand disconnect. Per-app VPN connections triggered by a provisioned application have sessions deleted correctly after an on-demand disconnect timeout.|
|596581||On iOS 9, if users create a VPN configuration that uses a client certificate, then deletes the Edge Client app, the certificate is removed as well.|
Fixes in 2.0.8
|547430||Previously, when an Edge Client configuration provisioned for client certificate authentication on iOS 9 was deleted, the client certificate was also deleted from the system store. This has been fixed.|
|562104||Previously, when Edge Client connected or reconnected to a VPN connection, the iOS VPN framework failed to download the Proxy AutoConfiguration (PAC) file and failed to apply the settings specified in the Network Access resource. Because of this, users were unable to access websites that required proxy settings in place. This issue is resolved.|
|578975||Previously, when users opened the Edge Client app on an iPad Pro, the client loaded but did not display the connection screen or the menu bar at the bottom. Users only saw the background. This could occur when users launched a new instance of the app rather than an application running in the background. This issue is resolved. The app user interface now displays correctly when users either launch the app or bring it up from the background.|
Contacting F5 Networks
For additional information, please visit http://www.f5.com.
You can find additional support resources and technical documentation through a variety of sources.
F5 Networks Technical Support
Free self-service tools give you 24x7 access to a wealth of knowledge and technical support. Whether it is providing quick answers to questions, training your staff, or handling entire implementations from design to deployment, F5 services teams are ready to ensure that you get the most from your F5 technology.
AskF5 is your storehouse for thousands of solutions to help you manage your F5 products more effectively. Whether you want to search the knowledge base periodically to research a solution, or you need the most recent news about your F5 products, AskF5 is your source.
The F5 DevCentral community helps you get more from F5 products and technologies. You can connect with user groups, learn about the latest F5 tools, and discuss F5 products and technology.
- Weekly HTML TechNews
- The weekly TechNews HTML email includes timely information about known issues, product releases, hotfix releases, updated and new solutions, and new feature notices. To subscribe, click TechNews Subscription, complete the required fields, and click the Subscribe button. You will receive a confirmation. Unsubscribe at any time by clicking the Unsubscribe link at the bottom of the TechNews email.
- Periodic plain text TechNews
- F5 Networks sends a timely TechNews email any time a product or hotfix is released. (This information is always included in the next weekly HTML TechNews email.) To subscribe, send a blank email to firstname.lastname@example.org from the email address you are using to subscribe. Unsubscribe by sending a blank email to email@example.com.