Increase granularity of NSAppTransportSecurity

Originator:stephen.darlington
Number:rdar://22209640 Date Originated:10-Aug-2015 11:38 AM
Status:Open Resolved:
Product:iOS Product Version:9b5
Classification:Enhancement Reproducible:Always
 
Summary:

I’m having a tricky time implementing NSAppTransportSecurity in a couple of my apps (at least without applying a global exception which defeats the point). They need to have insecure (http) access to the web but, in programatic terms, they only need that access in very specific parts of the app.

If it were possible to define exceptions to NSAppTransportSecurity for specific classes or (possibly) frameworks it would allow me to enforce https access to the sites that I know about in advance for the majority of the app, but still make the rest of the app work.

Notes:

For context, this is the only code that needs unfettered access in two of my apps: https://github.com/sdarlington/WSLHTMLEntities

The URLs passed in come from the user, so the app has no way of knowing whether a https version of the site exists (or, if it does, whether it’s the same as the http version).

Comments

Closed as a duplicate of rdar://20783976.

By stephen.darlington at Sept. 2, 2015, 9:17 a.m. (reply...)

Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!