News for hackers. Stuff that matters.

A comment on Google’s look, evolved. Parent comment

Re:Google’s look, evolved by Ciantic on Tuesday September 01, 2015 @01:11PM (#10154002)
New favicon? https://www.google.com/favicon.ico - is still the old one.
[ Parent | on HN ]
Re:Google’s look, evolved by sirn on Tuesday September 01, 2015 @02:22PM (#10154574)
The new one probably not populated to all their location yet, but adding a random query string does the trick.

https://www.google.com/favicon.ico?newlogo

(I'm seeing a four-colors capitalize G.)

[ Parent | on HN ]
Re:Google’s look, evolved by Eupolemos on Tuesday September 01, 2015 @03:24PM (#10155023)
I don't think that works very well as a favicon - I see a "c" first and then my eyes have to force it into a G.

Thank you for linking it, hadn't reached my interwebs yet.

[ Parent | on HN ]
Re:Google’s look, evolved by ljk on Tuesday September 01, 2015 @05:38PM (#10155937)
why does adding "?" work at getting a different logo? not a web guy here
[ Parent | on HN ]
Re:Google’s look, evolved by sirn on Tuesday September 01, 2015 @06:06PM (#10156122)
I'm not sure how it works at Google, but adding a random query string usually helps because of how proxy servers handle caching. Proxy servers usually treat an URL with different query string as different resource and cache them separately (e.g. /posts?page=2 is definitely not the same as /posts?page=1).

This is not only applies to caching by ISP, but also includes caching by the website itself as well (some websites put proxy in front of their server to cache rarely changed portion of the site, or even using CDN.).

[ Parent | on HN ]
Re:Google’s look, evolved by ljk on Tuesday September 01, 2015 @06:48PM (#10156326)
interesting, thanks!
[ Parent | on HN ]
Re:Google’s look, evolved by f0under on Tuesday September 01, 2015 @06:57PM (#10156376)
Anything after "?" is a query parameter that the server can read and then apply additional logic to for a response. In this case, they have code that responds to new logo and returns the new logo instead of the previous one.
[ Parent | on HN ]
Re:Google’s look, evolved by yamaneko on Tuesday September 01, 2015 @10:15PM (#10157067)
It's actually not querying anything, since it works for any query you pass. What happens is that you're bypassing cache because you're loading a different page, as explained by sirn above.

https://www.google.com/favicon.ico?anyquery

[ Parent | on HN ]
Re:Google’s look, evolved by bostonpete on Tuesday September 01, 2015 @04:21PM (#10155393)
Looks like Google's search pages pull the favicon from here: https://www.google.com/images/branding/product/ico/googleg_l...
[ Parent | on HN ]
Re:Google’s look, evolved by raldi on Tuesday September 01, 2015 @06:23PM (#10156212)
How'd you figure that out?
[ Parent | on HN ]
Re:Google’s look, evolved by phs2501 on Tuesday September 01, 2015 @07:30PM (#10156516)
From the <link rel="shortcut icon"> presumably.
[ Parent | on HN ]
Re:Google’s look, evolved by davidw on Tuesday September 01, 2015 @02:35PM (#10154670)
That big colorful G is much nicer than the squiggly blue lowercase one.
[ Parent | on HN ]
Re:Google’s look, evolved by mkagenius on Tuesday September 01, 2015 @02:20PM (#10154559)
Wondering the same. If it has changed, then ISP cache will take some time to reflect.
[ Parent | on HN ]
Re:Google’s look, evolved by teraflop on Tuesday September 01, 2015 @03:23PM (#10155015)
If your ISP is caching HTTPS requests, you have a problem.
[ Parent | on HN ]
Re:Google’s look, evolved by plonh on Wednesday September 02, 2015 @12:31AM (#10157431)
CDNs get copies of SSL keys so they can do their job: serving data. They are logically part of the serving infrastructure for example.com
[ Parent | on HN ]
Re:Google’s look, evolved by teraflop on Wednesday September 02, 2015 @03:47AM (#10157925)
Citation? Maybe some sites do that, but I find it really hard to believe that Google issues keys with a CN of "*.google.com" to anyone else.
[ Parent | on HN ]