Windows 8.1 allows only https URIs, not http URIs
- Clients - Windows 8.1
- Servers - Windows Server 2012 R2
While apps built for Windows 8 can include http and https URIs in their application content URIs, apps built for Windows 8.1 may include only https URIs.
The only exception is for dynamic ContentUriRules that are specified in the app’s AppxManifest.xml file. With dynamic ContentUriRules, apps can access additional domains or network resources that are provided by the admin, such as Group Policy URIs. However, dynamic ContentUriRules are only available to Windows Store apps if they meet these conditions:
- The Group Policy is enabled
- The package has specified the enterpriseAuthentication capability
- The package’s OSMaxVersionTested is Windows 8.1 or greater
When running an app built for Windows 8 on Windows 8.1, the use of http URIs in the ApplicationContentUriRules is allowed.
We recommend that WWA developers switch from <iframe> to the WebView control (<x-ms-webview>). However, if you need support for AppCache, IndexedDB, geolocation, or programmatic clipboard access, you will need to continue using <iframe> for Windows 8.1.
Continued usage of <iframe> for remote content will require a new entry in the ApplicationContentUriRules for the app. Apps with WebView require new entries in the ApplicationContentUriRules if the web content needs to invoke window.external.notify for generating a ScriptNotify event. If you do not have Visual Studio, you can update the app manifest by adding the following XML, including wildcards for subdomains (e.g. https://*.microsoft.com):
<Package> … <Applications> <Application> … <ApplicationContentUriRules> <Rule Match="https://www.example.com" Type="include"/> </ApplicationContentUriRules> </Application> </Applications> </Package>
- <iframe> element | <iframe> object
- Webview class
- WebView.ScriptNotify event