In reponse to John’s post about Why is Google hosting common Javascript/AJAX Libraries…
Google AJAX Loader API makes extra HTTP calls to do stat tracking on loads of the JS APIs (ie http://www.google.com/uds/stats?r0=el%7Cprototype ) A GET request is sent, and along with it a handful of cookies (perhaps the standard Google cookies, perhaps not - haven’t looked). Any ideas whats burried in there? See the attached request graph for an example.
Subsequent loads of a lib do make another HTTP request, which results in a 304 Not Modified response, but the request is also trackable. Bypassing the loader and getting at the JS libs directly does not cause the stat tracking to be called (and no cookies).
