Closed bluefirepatrick closed 9 years ago
Thanks, but let's merge to develop
, not master
:)
By the way, given that some EPUB3 e-books may contain references to non-secured (not HTTPS) external audio/video media assets, it does seem to make sense to use the proposed "allow everything" strategy:
<key>NSAppTransportSecurity</key>
<dict>
<key>NSAllowsArbitraryLoads</key>
<true/>
</dict>
In theory, it should be possible to specify an HTTP whitelist, but because this would have to be based on known domains, it is probably unrealistic:
<key>NSAppTransportSecurity</key>
<dict>
<key>NSExceptionDomains</key>
<dict>
<key>readium.org</key> <!-- what about 127.0.0.1 ? -->
<dict>
<key>NSIncludesSubdomains</key>
<true/>
<key>NSTemporaryExceptionAllowsInsecureHTTPLoads</key>
<true/>
</dict>
</dict>
</dict>
Oops, meant for pull request to be for 'develop' thanks
This fixes the error that is caused in the launcher when non https resources are loaded due to the new security restrictions in iOS 9