From http://www.techradar.com/us/news/internet/how-the-amazon-silk-browser-works-1036102 : """ Another interesting trick: Silk keeps track of this parsing. Jenkins says Silk can keep track of how the processing worked for, say, the last 100,000 users - that in all cases, the same logo header was downloaded and that the page did not change this routine. When you visit using the browser, Silk might decide to use a "smart push" and send you that logo header to speed up browsing even further. """ As far as trust, a browser will trust an explicitly configured forward proxy for http:// resources. For https://, we will tunnel through with CONNECT and do SSL to the origin over the tunnel. On Tue, Jul 2, 2013 at 9:56 AM, Sam Pullara <spullara@gmail.com> wrote: > On Jul 2, 2013, at 9:52 AM, Martin Thomson <martin.thomson@gmail.com> > wrote: > > On 2 July 2013 09:44, James M Snell <jasnell@gmail.com> wrote: > >> In other > >> words, we say that PUSH_PROMISE MUST NOT include :host or :scheme > >> and that clients MUST ignore them if they are sent. > > > > I don't like the prohibition because it's too simple. > > > > Say I do have, as Will points out, a forward proxy. One huge > > advantage that proxy could provide is push for cross-domain resources. > > Do you expect the proxy to parse the HTML of the initial request and push > down the resources that it finds in the document? I'm just wondering what > the implementation of this would look like. Why would the client trust > these resources are from the domains that the proxy claims? > > Sam > > >
Received on Tuesday, 2 July 2013 17:06:00 UTC