On Jul 2, 2013, at 10:05 AM, William Chan (陈智昌) <willchan@chromium.org> wrote: > 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. Got my forward and reverse proxy confused. Makes sense for HTTP with a trusted forward proxy — however, that doesn't mean that every HTTP connection should be able to send HTTP resources for any URL. This seems like it should be limited to trusted forward proxies and only over HTTP. Sam
Received on Tuesday, 2 July 2013 17:10:05 UTC