The initial request is the GoogleURLTracker class, which manages what Google TLD you're on. On the trunk, this won't happen if your default search engine is not Google, and even if it does happen, we won't save/update any cookies as a result of the update request.
Also, the reporter is using a binary downloaded from the continuous builder, that's why RLZ is included.
Did he clear the browsing data, too? I don't use Chromium, but I've seen similar requests with other browsers. The only way I have found to get the browser to stop sending the requests is to zorch all the browsing history, saved cookies, cached garbage, burn the village to the ground and sacrifice small birds. Of course, as soon as you search for soemthing against google.com, the requests will happily start up again.
says "Chromium will also continue to exist as it always has, without any RLZ library included. And, you can still download a Google Chrome with no RLZ behavior at www.google.com/chrome. But now that RLZ is open, Google Chrome distributed through promotional means will include this open-source implementation of RLZ.".
So what makes the continuous Chromium build a "Google Chrome distributed through promotional means"?
> What makes the continuous Chromium build a "Google Chrome distributed through promotional means"?
The continuous builders exist to compile and test all the code. Therefore they build with RLZ options enabled.
The continuous build binaries are literally whatever the state of the tree happened to be at the time. They're useful for bisection but people aren't expected to run them for non-development reasons.
Well that's very misleading, even Wikipedia thinks that : " Google confirmed that the RLZ tracking token [...] [is] not in versions of Chrome downloaded from the Google website directly or in any versions of Chromium."
From the thread: "We think that the reported RLZ ping behavior (that request to "/tools/pso/ping...") is a regression -- RLZ pings should not be happening in Chromium or non-promotional Google Chrome builds, so this is not the intended behavior."
I'm more concerned about the opt-out "safe browsing" feature CCing Google on all your requests, complete with ID cookie. When did that cease to be a cardinal sin? Didn't Palm get reamed for that recently?
It doesn't do that on all your requests, does it? I thought everyone did that via local bloom table (or similar structure), and checking with a central backend only when it gets a potential hit.
My bad, it does not appear to be hitting the safe browsing service on every request but just a few times soon after the first request of a session. I guess it's probably just updating the bloom filter.
They're still not off the hook for doing autocomplete on the server by default. That effectively gives them every typed in URL.
http://inari.aerdan.org/gallery/chromeopts.png
The initial request is the GoogleURLTracker class, which manages what Google TLD you're on. On the trunk, this won't happen if your default search engine is not Google, and even if it does happen, we won't save/update any cookies as a result of the update request.
Also, the reporter is using a binary downloaded from the continuous builder, that's why RLZ is included.