[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
IOS new versions and network load
- Subject: IOS new versions and network load
- From: valdis.kletnieks at vt.edu (valdis.kletnieks at vt.edu)
- Date: Mon, 18 Sep 2017 12:14:11 -0400
- In-reply-to: <154b1c7f-3479-4fce-a201-97c9afeab918@Spark>
- References: <[email protected]> <CAHf3uWxoFNXx7-6xComzPLohbzPw6SkLsO34AXSKi8KhXxZR7Q@mail.gmail.com> <[email protected]> <CAHf3uWyq1SjJHJMCLKBjvYUrn+=LsqJyyV76msgt4TvEUgn+0g@mail.gmail.com> <[email protected]> <1912716896.66776.1505738890500.JavaMail.mhammett@ThunderFuck> <[email protected]> <[email protected]> <154b1c7f-3479-4fce-a201-97c9afeab918@Spark>
On Mon, 18 Sep 2017 16:57:55 +0100, Marco Slater said:
> > While we don���t use Apple's caching servers we do have transparent caching
> > in place which nets us about 82% of their content being serverd locally. On a
> > big IOS update it will probably be close to 99% for that one title.
> Would you be open to elaborating a bit on how that���s set up on your network? :)
I'm particularly interested in how they introspect https:// targets. Apple *IS* using
https:// (or other TLS-secured connections), right?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 486 bytes
Desc: not available
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20170918/5f427623/attachment.sig>