Path: csiph.com!aioe.org!.POSTED!not-for-mail From: =?UTF-8?Q?Arne_Vajh=c3=b8j?= Newsgroups: comp.lang.java.programmer Subject: Re: SSL trends Date: Sat, 24 Sep 2016 18:29:27 -0400 Organization: Aioe.org NNTP Server Lines: 28 Message-ID: References: NNTP-Posting-Host: 7SK6yTFfqwlIPNBLl3l7Qg.user.gioia.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-Complaints-To: abuse@aioe.org User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 X-Notice: Filtered by postfilter v. 0.8.2 Xref: csiph.com comp.lang.java.programmer:35642 On 9/23/2016 1:02 AM, Roedy Green wrote: > On Thu, 15 Sep 2016 20:18:10 -0400, Arne Vajhøj > wrote: > >>> 4. caching is turned off >> >> Wrong. > > If you have two users accessing the same page, but it is a secret what > they are accessing, how can a cache possibly share that page? > > Obviously you can do things like disk caching on the server using the > unencrypted form, but once the page is encrypted, e.g. the first page > of an online newspaper, it is not going to get cached by a the IAP > from its local cache. The browser can and do cache pages retrieved via HTTPS. It can be cached server side as well. That is done by terminating SSL in front on the cache server. That is quite common. The only cache that is not possible is an intermediate cache somewhere in the middle of the network. I don't think I have heard about that being used on this side of year 2000. Arne