Re: App Transport Security exceptions App Store signed app

> On Jan 27, 2016, at 7:14 PM, Alex Zavatone wrote: > > Here’s another discussion on nscurl that might help from Quinn at Apple DTS > with a little more info. Thanks for the tip, Gavin. .. Quinn’s a god! .. Here’s the CocoaHeads presentation I mentioned:

Re: App Transport Security exceptions App Store signed app

> On Jan 27, 2016, at 12:55 AM, Trygve Inda wrote: > > Calls to http on my domain (xericdesign.com) work. Calls via http to my > other domain (earthdeskcloudhost02.com) do not work. .. you (and others) may find this option on the nscurl command nscurl

Re: App Transport Security exceptions App Store signed app

Here’s another discussion on nscurl that might help from Quinn at Apple DTS with a little more info. Thanks for the tip, Gavin. https://forums.developer.apple.com/thread/14816 On Jan 27, 2016, at 7:02 PM, Gavin Eadie wrote: >> On Jan 27, 2016, at 12:55 AM, Trygve Inda

Re: App Transport Security exceptions App Store signed app

> Also, have you looked into setting up HTTPS on those servers instead of > working around its absence? Part of the reason Apple added ATS was to nudge > app developers to make their network connections more secure, which will > benefit users. It is basically a cost issue. It is expensive to set

Re: App Transport Security exceptions App Store signed app

> On 26 Jan 2016, at 9:55 pm, Trygve Inda wrote: > >> connection failed: (null) The resource could not be loaded because the App >> Transport Security policy requires the use of a secure connection. >> http://www.earthdeskcloudhost02.com/mosaic/free/clouds-2048.jpg > >

Re: App Transport Security exceptions App Store signed app

On Tue, Jan 26, 2016 at 11:18 PM, Jens Alfke wrote: > I believe you’re using the wrong key. If you need non-SSL connections to > work, the key you want is NSAllowsArbitraryLoads. The key you’re using is > for situations where you make an SSL connection but the SSL server

Re: App Transport Security exceptions App Store signed app

> On Jan 27, 2016, at 7:53 AM, Sixten Otto wrote: > > According the docs, it's also for the case where the connection needs to be > made over non-S HTTP: "With this key’s value set to YES >

Re: App Transport Security exceptions App Store signed app

> On Jan 27, 2016, at 7:32 AM, Trygve Inda wrote: > > It is basically a cost issue. It is expensive to set up SSL certificates on > 8 different servers... It would cost us about $700/yr Sounds like you’re being overcharged. SSL on hosted domains used to be pricey

Re: App Transport Security exceptions App Store signed app

On Wed, Jan 27, 2016 at 10:29 AM, Jens Alfke wrote: > I believe that text refers to an *SSL* server "with no certificate, or a > self-signed, expired, or hostname-mismatched certificate”. There is a > _separate_ key that allows non-SSL connections. > Reading over the rest of

Re: App Transport Security exceptions App Store signed app

> >> On Jan 27, 2016, at 7:32 AM, Trygve Inda wrote: >> >> It is basically a cost issue. It is expensive to set up SSL certificates on >> 8 different servers... It would cost us about $700/yr > > Sounds like you’re being overcharged. SSL on hosted domains used to be

Re: App Transport Security exceptions App Store signed app

On Tue, 26 Jan 2016 22:18:45 -0800, Jens Alfke said: >Also, have you looked into setting up HTTPS on those servers instead of >working around its absence? Part of the reason Apple added ATS was to >nudge app developers to make their network connections more secure, >which will benefit users.

Re: App Transport Security exceptions App Store signed app

On 26 Jan 2016, at 9:55 pm, Trygve Inda wrote: > connection failed: (null) The resource could not be loaded because the App > Transport Security policy requires the use of a secure connection. > http://www.earthdeskcloudhost02.com/mosaic/free/clouds-2048.jpg I'm no App

Re: App Transport Security exceptions App Store signed app

> On Jan 26, 2016, at 9:55 PM, Trygve Inda wrote: > > NSTemporaryExceptionAllowsInsecureHTTPLoads The “Temporary” in those names was only needed for the first iOS 9 beta. It might still be supported, but the official names do not have Temporary in them. See the

App Transport Security exceptions App Store signed app

I am still getting an error despite my Info.plist beign configured correctly (as far as I can tell). Calls to http on my domain (xericdesign.com) work. Calls via http to my other domain (earthdeskcloudhost02.com) do not work. connection failed: (null) The resource could not be loaded because the