October 2017 - Macnetworkprog

Re: 'Global' NSURLCache?
by Quinn "The Eskimo!" 31 Oct '17

31 Oct '17

site_archiver(a)lists.apple.com Delivered-To: macnetworkprog(a)lists.apple.com On 28 Oct 2017, at 03:11, sebastienboisvert(a)yahoo.com wrote: > I'd like to understand the reasoning behind making NSHTTPStorage globally > available to all apps vs. NSURLCache being per-app only. To start, the cookie store is not global, it’s per user. That level of sharing is grandfathered in from the very early days of NSURLConnection, which was really just the back end of Safari factored out for everyone to use. At the time it made sense for Safari and all the user’s apps to share a cookie store. These days, of course, that policy is considered security madness. Across all of our platforms the only apps that share Safari’s cookie store are non-MAS apps on the Mac. Everything else has its own cookie store (although they can share cookie stores via App Groups). As to the difference between the cookie store and the cache, I suspect that’s an artefact of the implementation. Back in the day both were stored as simple files on disk. Obviously it’s a pain to coordinate shared access to such files. Doing this for cookies was considered important, so the implementers came up with a (clunky) scheme for that. Doing it for the cache wasn’t important — and it’s much harder due to the expected access patterns for the cache — so the caches were left separate. On modern systems the cookie store and cache are actually managed by a <x-man-page://8/nsurlstoraged>, so this coordination is much easier. This is what enables, for example, each App Group to have a shared cookie store. If you want to share a cache between processes you may be able to do that by having them both initialise an NSURLCache instance to point to the same place on disk (using `-initWithMemoryCapacity:diskCapacity:diskPath:`). I /think/ that’ll work but I haven’t looked into it in detail so I’m not 100% sure. If you need a definitive answer to the last point I recommend that you open a DTS tech support incident for it. That’ll allow me to spend time researching it properly. <https://developer.apple.com/support/technical/> Share and Enjoy -- Quinn "The Eskimo!" <http://www.apple.com/developer/> Apple Developer Relations, Developer Technical Support, Core OS/Hardware _______________________________________________ Do not post admin requests to the list. They will be ignored. Macnetworkprog mailing list (Macnetworkprog(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/macnetworkprog/site_archiver%40list… This email sent to site_archiver(a)lists.apple.com

1 0

Re: 'Global' NSURLCache?
by sebastienboisvert＠yahoo.com 30 Oct '17

30 Oct '17

site_archiver(a)lists.apple.com Delivered-To: macnetworkprog(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1509382341; bh=SlX94FYeugdzaFwJrgYLakDNbXEwrYu43bJNnwRgHI8=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From:Subject; b=pnMQktztPP/kItat/zRKXLHG1fXy9enNCiglBzwbP25LFilcWasch4iQa9fv/j58idqdOE5AIaUGtaxhU8ZlNp2MOMRKbv2Dmycjdo0ZjeL5cP3oyZ7j5U0muqNAEVSGsT5q5Yp7AdTluASNZeUXpLOdGkOUvk/tFeGnNfkpd5O2FcfjkwqoslsDcnV3ecT0sPbIvT4uub8TpMP+8eCMur8DAcJCQiPfmKK18mzs10/ZmhIOkNaYkHh9IxJK8ac5AuiLCi9vTbl0EwQVmodOZXHh/eIf29Yzt0Qt6NMjV90RGBxYqhEdCYH+sALvx0aZ/K5zImvIysZMMWLJNf4KwQ== > On Oct 30, 2017, at 3:45 AM, Quinn The Eskimo! <eskimo1(a)apple.com> wrote: > > Three points to clarify: > > * On 28 Oct 2017, at 03:11, sebastienboisvert(a)yahoo.com wrote: > >> From my understanding given the docs, there doesn't seem to be a way to have >> a 'global' NSURLCache that can be truly shared between two separate >> applications. > > There’s no mention of the platform you’re working. While I suspect you’re > referring to macOS, it’d be nice to confirm that. > > * If you are working on the Mac, are you targeting Mac App Store or Developer > ID? Yes, referring to macOS in this case. Not targeting MAS. > > * You wrote: > >> I'd like to understand the reasoning behind making NSHTTPStorage globally >> available to all apps vs. NSURLCache being per-app only. > > `NSHTTPStorage` isn’t a system class. You mean `NSHTTPCookieStorage`, right? Correct, meant the cookie storage class. > > Share and Enjoy > -- > Quinn "The Eskimo!" <http://www.apple.com/developer/> > Apple Developer Relations, Developer Technical Support, Core OS/Hardware > > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Macnetworkprog mailing list (Macnetworkprog(a)lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/macnetworkprog/sebastienboisvert%40… > > This email sent to sebastienboisvert(a)yahoo.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Macnetworkprog mailing list (Macnetworkprog(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/macnetworkprog/site_archiver%40list… This email sent to site_archiver(a)lists.apple.com

1 0

Re: 'Global' NSURLCache?
by Quinn "The Eskimo!" 30 Oct '17

30 Oct '17

site_archiver(a)lists.apple.com Delivered-To: macnetworkprog(a)lists.apple.com Three points to clarify: * On 28 Oct 2017, at 03:11, sebastienboisvert(a)yahoo.com wrote: > From my understanding given the docs, there doesn't seem to be a way to have > a 'global' NSURLCache that can be truly shared between two separate > applications. There’s no mention of the platform you’re working. While I suspect you’re referring to macOS, it’d be nice to confirm that. * If you are working on the Mac, are you targeting Mac App Store or Developer ID? * You wrote: > I'd like to understand the reasoning behind making NSHTTPStorage globally > available to all apps vs. NSURLCache being per-app only. `NSHTTPStorage` isn’t a system class. You mean `NSHTTPCookieStorage`, right? Share and Enjoy -- Quinn "The Eskimo!" <http://www.apple.com/developer/> Apple Developer Relations, Developer Technical Support, Core OS/Hardware _______________________________________________ Do not post admin requests to the list. They will be ignored. Macnetworkprog mailing list (Macnetworkprog(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/macnetworkprog/site_archiver%40list… This email sent to site_archiver(a)lists.apple.com

1 0

'Global' NSURLCache?
by sebastienboisvert＠yahoo.com 28 Oct '17

28 Oct '17

site_archiver(a)lists.apple.com Delivered-To: macnetworkprog(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1509156702; bh=dB/USDbNLijV5lzaAXt5k9xYEcLGePIxbI3AZOp8az0=; h=From:Subject:Date:To:From:Subject; b=YI34R6p0LiHfb37wnMpW29LlaG4x3+1DilucwLHuGZInmMaZSALHN+9YZhxypGIxmlknNIOROCrvqONO6Vv1UBf/5k/cXzivsPY9d1yK2lnmOlsqWsoSikBp2ZQ2mvBzG28esvl6FLEqe9Hag+HvH+O+cRJgcKjpUJQZgGEMx6xyjSXOVFYtXO2+AhHaV8+oCPoxs+6jZMTXz+uzDmeonnpcchKjY1elYtKkOVnb52GyAECLHl1wF80F6vRpj+ZVOtYjP+9QLZUPBtdJ8JDNh2z1lUnRdJ+OuzC4lMKPRWrLONBkN5mEnBgy16Rb3byoaXB2jAqe4BnM4+NWBYLy4w== >From my understanding given the docs, there doesn't seem to be a way to have a 'global' NSURLCache that can be truly shared between two separate applications. But I'll ask anyway: 1. Would it be possible for two apps to share a custom NSURLCache (perhaps by referring the same disk path)? 2. I'd like to understand the reasoning behind making NSHTTPStorage globally available to all apps vs. NSURLCache being per-app only. I can't see security being a compelling reason given the information stored in cookies, which doesn't really leave any obvious reasons why NSURLCache isn't global. _______________________________________________ Do not post admin requests to the list. They will be ignored. Macnetworkprog mailing list (Macnetworkprog(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/macnetworkprog/site_archiver%40list… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Why does NSURLSession return NSURLResponse instead of NSHTTPURLResponse
by sebastienboisvert＠yahoo.com 19 Oct '17

19 Oct '17

site_archiver(a)lists.apple.com Delivered-To: macnetworkprog(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1508445571; bh=bF9rKT+WrON0zaf35fYSnJPEvekLRMcBcnNQ2Zp0p3M=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From:Subject; b=CBZFcqNV9CVjYkSzVYmFW4pANZkqEAMOa3jdVC9rj80ZOyHoK+LpkGXo4/AcsclmGqdmufH6swHkp7EF6r2XYb1q3PgKbVenlYbMqUlTCMOjro/8XK+6jxa8ulJFdzJjDp7gNcgv/MYtOai19k9qDSPxRmeWaTHBY7TiNPiGued/nHymsCXrYNsHhzFUfTt61yOVfc2CVHwNBzJnRg5i6yR+ufsQz6Je0KnC2IKhYF6GDQUikyH9QWnS6Om0wGqbKJv39KEbhcfYyqZVxAAwMmGyb4uEvL/weV+QteFC+jnxDM1HM1bZ8Fw4m4wZ6VQVjjYzQd6UvRlIvSEXx9W7cg== Thanks for the replies everyone, to answer some of the questions: > On Oct 18, 2017, at 3:53 AM, Quinn The Eskimo! <eskimo1(a)apple.com> wrote: > > Some questions / suggestions for moving this forward: > > * Do you have any NSURLProtocol subclasses in play here? No other custom URL protocols involved > > * Are you sure that the crash is because you got an NSURLResponse? If you > have some other problem you could get a similar looking crash. In > Objective-C I typically write this: > > NSHTTPURLResponse * httpResponse = (NSHTTPURLResponse *) response; > assert([httpResponse isKindOfClass:[NSHTTPURLResponse class]); > > so I’d trap this error immediately. > > * You could add a trap like this: > > assert([response.URL.scheme isEqual:@"http"]); I put both asserts in, with the 'https' check first, and it always caught on the class check. > > * You might want to enable a CFNetwork diagnostic log, per QA1887. If you > can reproduce the crash with that logging enabled, it might reveal something > interesting. > > <https://developer.apple.com/library/content/qa/qa1887/_index.html> > This was helpful. The diagnostic showed that it was returning a cached response, so I looked further into my code that adds to the cache. In order to avoid hitting our server for future GETs, I use a custom NSURLCache, that is also set to be used on the URL session's configuration; when I push new data up to our server, I pre-cache the data to that URL cache by creating a NSCachedURLResponse along with some additional metadata for housekeeping purposes. I think the problem was in the order I was adding the cached response relative to the session request - the cached response would get added soon after the session task was initiated, but before its completion block was called, which seemed to make the session pick up that cached response at some point. Moving the caching step to within the completion block solved the issue in my case. _______________________________________________ Do not post admin requests to the list. They will be ignored. Macnetworkprog mailing list (Macnetworkprog(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/macnetworkprog/site_archiver%40list… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Why does NSURLSession return NSURLResponse instead of NSHTTPURLResponse
by Quinn "The Eskimo!" 18 Oct '17

18 Oct '17

site_archiver(a)lists.apple.com Delivered-To: macnetworkprog(a)lists.apple.com On 17 Oct 2017, at 23:05, Sebastien Boisvert <sebastienboisvert(a)yahoo.com> wrote: > What would make it a NSURLResponse (when a valid response is returned) > instead of a NSHTTPURLResponse? As Jens said, it’s correct to rely on the response being an NSHTTPURLResponse when the request’s URL is `http://` or `https://`. I’ve been working with NSURLSession (and before that NSURLConnection) for about as long as Jens has, and it’s always worked that way. I work in Swift mostly these days, and my completion handlers tend to include this: let response = response as! HTTPURLResponse … test response.statusCode … which is going to hard crash if this fails. The only situations I know of where you’ll get `NSURLSession` are: * You pass in a request whose URL uses some other scheme, for example, `ftp://` * You’ve implemented a custom NSURLProtocol subclass for HTTP-sytle requests and create the wrong response [1] * * * Some questions / suggestions for moving this forward: * Do you have any NSURLProtocol subclasses in play here? * Are you sure that the crash is because you got an NSURLResponse? If you have some other problem you could get a similar looking crash. In Objective-C I typically write this: NSHTTPURLResponse * httpResponse = (NSHTTPURLResponse *) response; assert([httpResponse isKindOfClass:[NSHTTPURLResponse class]); so I’d trap this error immediately. * You could add a trap like this: assert([response.URL.scheme isEqual:@"http"]); * You might want to enable a CFNetwork diagnostic log, per QA1887. If you can reproduce the crash with that logging enabled, it might reveal something interesting. <https://developer.apple.com/library/content/qa/qa1887/_index.html> Share and Enjoy -- Quinn "The Eskimo!" <http://www.apple.com/developer/> Apple Developer Relations, Developer Technical Support, Core OS/Hardware [1] Back in the day this was a tricky because NSHTTPURLResponse has no public initialisers but that was fixed OS X 10.7 / iOS 5.0. _______________________________________________ Do not post admin requests to the list. They will be ignored. Macnetworkprog mailing list (Macnetworkprog(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/macnetworkprog/site_archiver%40list… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Why does NSURLSession return NSURLResponse instead of NSHTTPURLResponse
by Jens Alfke 18 Oct '17

18 Oct '17

site_archiver(a)lists.apple.com Delivered-To: macnetworkprog(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=c3H9uk4e/UffWhGyG53sVcDWvBqcb lACkP4iXDBrZeM=; b=bS/FXJX2kZPTXQILboo2U0sYVggKnszO2j/HP2MEqSsiw 7B2kBCjZD14PX/dtWDEpZ7mSdSI0W+h5iBBWtmSTTsTqKiFeYt4alBmP1e8nLFBz 6N9kwE/DY7CEBIQFkJgXOEZcBf06sUzE0YWM9n19S656KE2Z2VDVuE53Hb28pYBS i6IAUmszBVLaQqw0Xf5ZAjd8n7c3ZRh+8LFeNf+8M4Gp9vUU26wvskkpcbBI1nJX ty2jjSrixERs+yig1Y68xtWihdV2sawIDTa+goiHjnXUuRrJpNRJUlUuHXf6nPQt t9YdplIxS5p3vZ0QbUe0xAjviUg5c+h3FRxDTPFNA== > On Oct 17, 2017, at 10:54 PM, じょいすじょん <dangerwillrobinsondanger(a)gmail.com> > wrote: > > The docs and call signature mostly say you'll get NSURLResponse, but that it > will be NSHTTPURLResponse if your request was HTTP or HTTPS. Yes, and this has been my experience since 2002. > Perhaps there is a bug. That’s what we’re trying to figure out. —Jens _______________________________________________ Do not post admin requests to the list. They will be ignored. Macnetworkprog mailing list (Macnetworkprog(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/macnetworkprog/site_archiver%40list… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Why does NSURLSession return NSURLResponse instead of NSHTTPURLResponse
by じょいすじょん 18 Oct '17

18 Oct '17

site_archiver(a)lists.apple.com Delivered-To: macnetworkprog(a)lists.apple.com > On Oct 18, 2017, at 14:18, Jens Alfke <jens(a)mooseyard.com > <mailto:jens@mooseyard.com>> wrote: > > > >> On Oct 17, 2017, at 5:06 PM, dangerwillrobinsondanger(a)gmail.com >> <mailto:dangerwillrobinsondanger@gmail.com> wrote: >> >> Isn’t NSHTTPURLResponse a subclass of NSURLResponse? > > Yes it is, but calling `((NSHTTPURLResponse*)response).statusCode` will still > throw an exception if the response isn’t actually an instance of the > subclass, because the base class doesn’t implement that property. > > —Jens That's exactly the point I think. The docs and call signature mostly say you'll get NSURLResponse, but that it will be NSHTTPURLResponse if your request was HTTP or HTTPS. Perhaps there is a bug. Either a docs bug worth filing if it should say you should always check if the response is an NSHTTPURLResponse or that it responds to selector statusCode Or a functional bug where sometimes it's not working. Sample code here shows the completionHandler passing an NSURLResponse not necessarily a subclass. https://developer.apple.com/library/content/documentation/Cocoa/Conceptual/… <https://developer.apple.com/library/content/documentation/Cocoa/Conceptual/…> The docs for dataTaskWithURL:completionHandler: say response An object that provides response metadata, such as HTTP headers and status code. If you are making an HTTP or HTTPS request, the returned object is actually an NSHTTPURLResponseobject. The docs show the signature as this - (NSURLSessionDataTask <https://developer.apple.com/documentation/foundation/nsurlsessiondatatask?l…> *)dataTaskWithURL:(NSURL <https://developer.apple.com/documentation/foundation/nsurl?language=objc> *)url completionHandler:(void (^)(NSData <https://developer.apple.com/documentation/foundation/nsdata?language=objc> *data, NSURLResponse <https://developer.apple.com/documentation/foundation/nsurlresponse?language…> *response, NSError <https://developer.apple.com/documentation/foundation/nserror?language=objc> *error))completionHandler; That does indeed seem to imply that it would return an NSURLResponse as a generality, but that you will in fact have an NSHTTPURLResponse object if your request was HTTP or HTTPS. Docs for dataTaskWithRequest:completionHandler: the same in all those key areas. Docs for downloadTaskWithURL:completionHandler: same. Docs for downloadTaskWithRequest:completionHandler: same. Docs for downloadTaskWithResumeData:completionHandler: same. Docs for uploadTaskWithRequest:fromData:completionHandler: same. uploadTaskWithRequest:fromFile:completionHandler: Docs for URLSession:dataTask:didReceiveResponse:completionHandler: get a little vague but the signature says NSURLResponse. URLSession:dataTask:didReceiveResponse:completionHandler: also vague. URLSession:dataTask:willCacheResponse:completionHandler: also vague, but NSCachedURLResponse seems a bit different. _______________________________________________ Do not post admin requests to the list. They will be ignored. Macnetworkprog mailing list (Macnetworkprog(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/macnetworkprog/site_archiver%40list… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Why does NSURLSession return NSURLResponse instead of NSHTTPURLResponse
by Jens Alfke 18 Oct '17

18 Oct '17

site_archiver(a)lists.apple.com Delivered-To: macnetworkprog(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=reNA7r w65C55ITEzK1fXMEbXcLkBuvaoCyLxMoJyYIw=; b=pJJDriz+//xw+Y/SeHW+Qh y9DEZJI3fYorXf4J37/QH+NFK19gKY0F6jHgHFA09welY3AOzV4xDmbEQ9gBmGJx 2XM5miZFlkwtoZmqsHyqtRioyjdMFA8i3WFsKj9pKNWy4gvoujzJ5o81f79d4Bx6 W0szlJq4YzJr3eTNmM6XkEstdPzSfZ5KzV7nl2x5NeWzcMk2ShJ2tCFfC+nuFEAf t7Bxt8QKsDgLubq7tx4eEdOJO7btgmFEmSg/o55XmowlSuJpzReYFpAC1uk7tS9J R958wYZ7gujYWojTKkkKakKdjO2bT5Tx3m6bAzaWKDNw4X9xXCgPACA1NKCpNTYA == > On Oct 17, 2017, at 5:06 PM, dangerwillrobinsondanger(a)gmail.com wrote: > > Isn’t NSHTTPURLResponse a subclass of NSURLResponse? Yes it is, but calling `((NSHTTPURLResponse*)response).statusCode` will still throw an exception if the response isn’t actually an instance of the subclass, because the base class doesn’t implement that property. —Jens _______________________________________________ Do not post admin requests to the list. They will be ignored. Macnetworkprog mailing list (Macnetworkprog(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/macnetworkprog/site_archiver%40list… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Why does NSURLSession return NSURLResponse instead of NSHTTPURLResponse
by dangerwillrobinsondanger＠gmail.com 18 Oct '17

18 Oct '17

site_archiver(a)lists.apple.com Delivered-To: macnetworkprog(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=X5RmV86iDMXpKbAPlCAY3DY62PkdeyvUQnmG3maEp5k=; b=XyqSnMqI1LFuu0x5VRkWshY0SJsnbH1GrOfBd9WpV8bKDQSjnGZdrC6cy213zmaB63 /7wCnDknR8a1KQfD5Yl5fpNz25Dm/pFMJ3VHlxNgCW4BiU5DOv2LYygRfWfdSkEeWKc6 vPjonmTyT17pTNipGdUEiSGfiXNW+kRfOrnu0g5aykAXoVwnHG5UGFtr7t8yrDyfJeZr JpWZ40Bg9Kl5nxyKZELGvZnxspmmi5To3Ww1Okxh2gQB1w0QPsSdG+nHYNFK3PeWRHkn 3+7M/nSnt5nQRJJoil/6Qxm82hVbUTu7G1pPk2BkUtHpCPKTIqQUa5uBq/Rpyz3tyl3D hvvg== Isn’t NSHTTPURLResponse a subclass of NSURLResponse? > On Oct 18, 2017, at 7:53, Jens Alfke <jens(a)mooseyard.com> wrote: > > > >> On Oct 17, 2017, at 3:05 PM, Sebastien Boisvert >> <sebastienboisvert(a)yahoo.com> wrote: >> >> I've noticed that most times, the response will come back as a >> NSHTTPURLResponse, other times only as a NSURLResponse (which leads to a >> crash when I try to get the -statusCode). > > I’ve never seen a request for an HTTP[S] URL return a response that wasn’t an > NSHTTPURLResponse, so that’s definitely unexpected! > > Are you certain that the URLs in your requests always have the scheme “http” > or “https”? > > —Jens > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Macnetworkprog mailing list (Macnetworkprog(a)lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/macnetworkprog/dangerwillrobinsonda… > > This email sent to dangerwillrobinsondanger(a)gmail.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Macnetworkprog mailing list (Macnetworkprog(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/macnetworkprog/site_archiver%40list… This email sent to site_archiver(a)lists.apple.com

1 0