Re: ATS fails for one subdomain, succeeds for another
site_archiver@lists.apple.com Delivered-To: macnetworkprog@lists.apple.com Dkim-signature: v=1; a=rsa-sha1; c=relaxed; d=red-sweater.com; h=from :content-type:content-transfer-encoding:mime-version:subject :date:references:to:in-reply-to:message-id; s=red-sweater.com; bh=ocA5Bm4fNdcW19Hlyuv81nH2ei0=; b=knXwSe2gDoE8il7iW0bFxGG6ea2N ra7xdTbDkms8EZ8zDpr76ARtSN7piXTsCU3QdYBAXXZCjqtvFtGlydYUSxA75Dc0 97jKDJ2eeO4wgDXWstIdcpEZEJqgUo+hNJk+MxUhBkf+8AVpxo+lI/qTBB1el8/S xX3Cr3IuOoc+uVk= Thanks Tom...
On Dec 4, 2017, at 4:11 PM, Tom Pusateri <pusateri@bangj.com> wrote:
There is an exception list for ATS in the Info.plist. Would sweatertest.wordpress.com be listed there?
Unless an http URL is in the exception list, it will always fail. (See NSExceptionDomains)
https://developer.apple.com/library/content/documentation/General/Reference/...
Tom
I think I understand the expected behavior. The diverging behavior is why I’m writing to the list. There are no exceptions in the list. Only “wordpress.com” with “includes subdomains” set to YES. These URLs obviously have HTTPS counterparts, and if allowed to connect via HTTP the server will redirect them. Monitoring the traffic for my app it doesn’t look like it actually does ever try to connect via HTTPS. This makes me wonder if the system is maintaining some kind of cache of domains that had previously been redirected from HTTP to HTTPS. Daniel _______________________________________________ Do not post admin requests to the list. They will be ignored. Macnetworkprog mailing list (Macnetworkprog@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/macnetworkprog/site_archiver%40lists... This email sent to site_archiver@lists.apple.com
participants (1)
-
Daniel Jalkut