Why does Google prepend while(1); to their JSON responses?

Re:Why does Google prepend while(1); to their JSON responses? by homakov on Sunday December 29, 2013 @11:32PM (#6983051)

my solution is request.xhr? check. the link above is only to explain what rails-bug was. I don't think checking referrer is a good idea there.

[ Parent | on HN ]

Re:Why does Google prepend while(1); to their JSON responses? by joev_ on Monday December 30, 2013 @12:09AM (#6983132)

Hey Egor, article author here. How come you are not such a fan of checking referer? It cannot be a global fix (some sites depend on serving xdomain scripts, have lots of users with proxies that alter headers etc), but it should work well for many cases no?

[ Parent | on HN ]

Re:Why does Google prepend while(1); to their JSON responses? by homakov on Monday December 30, 2013 @12:57AM (#6983265)

it works of course, but to be compatible with many environments we need something more reliable than Referrer.

[ Parent | on HN ]

Re:Why does Google prepend while(1); to their JSON responses? by tzury on Sunday December 29, 2013 @11:34PM (#6983052)

Sorry Egor, I thought you are pointing out an article you have published.

[ Parent | on HN ]

Re:Why does Google prepend while(1); to their JSON responses? by homakov on Sunday December 29, 2013 @11:40PM (#6983067)

This is joev's article. His explanations of the issue are better than mine ;)

[ Parent | on HN ]