Wow -- it seems very heavy-handed to force that on app developers (how do you build a web browsing app in that case?)
Does that apply to all network requests, or just the pages that can be loaded into the main application window? Your solution seems like a good one, though; just filter the unusable rules between the app-level configuration and the platform config, and warn the developer that it's happening. (At least I *think* that's what it's doing ;) ) On Tue, Aug 26, 2014 at 5:19 AM, Sergey Grebnov (Akvelon) < [email protected]> wrote: > Windows 8.1 and Phone 8.1 requires https for access rules[1], http is not > supported anymore. I've sent PR below [2] to prevent build failure and > trace warning message for this case. One of real cases where it is required > is mobile spec app which cannot' be built since it defines the following > rules. > > <access origin="http://audio.ibeat.org"; /> > <access origin="http://cordova-filetransfer.jitsu.com"; /> > <access origin="http://whatheaders.com"; /> > <access origin="http://*.apache.org"; /> > <access origin="https://*.apache.org"; /> > <access origin="http://www.google.com"; /> > <access origin="http://techslides.com"; /> > <access origin="httpssss://example.com" /> > > [1] > http://msdn.microsoft.com/en-us/library/windows/desktop/dn457654(v=vs.85).aspx > [2] https://github.com/apache/cordova-windows/pull/41 > > Thx! > Sergey >
