Chromium 7.0.544.0 issues http requests to clients2.google.com:443 and www.google.com:443

[Sig Weber]

I've verified this twice now and this is AFAIK a new behavior. I've
been testing this on Windows 7 x64 US-English with Chrome 6.0.472.63
and Chromium 7.0.544.0 (downloaded from
http://build.chromium.org/buildbot/snapshots/chromium-rel-xp/).

To track the http requests I've been using the free Fiddler debugging
proxy.

Both browsers do have the same configuration settings applied:

- Scroogle as default search engine (to circumvent the default search
engine ping if "Google" is selected).
- All privacy settings, like the phising and malware protection, are
turned off.
- The home page is set to "New Tab".
- On startup is set to reopen the last pages (which are empty on both
browsers).

When I fire up Chrome it does not ping any Google server (except when
I open the "About" dialog and it runs the check for an update - but
that's expected behavior).

However, when I fire up Chromium it start to issue requests to
clients2.google.com:443 and www.google.com:443 without me doing
anything (not even opening the "Options" dialog).

IMHO this is a regression in Chromium 7 from Chrome 6 I would be glad
if those strange requests could be turned off again (I'm working most
of my time with a 3G connection where I am charged by the KByte which
can become costly when you just have Chromium open with some local
HTML pages).

Cheers,

Sig

[PhistucK]

Do you still experience this issue?

If so, you should search crbug.com for an existing issue and star it. If you cannot find one, file a new issue at new.crbug.com.

Thank you.

☆PhistucK

--
Chromium Discussion mailing list: chromium...@chromium.org
View archives, change email options, or unsubscribe:
   http://groups.google.com/a/chromium.org/group/chromium-discuss

[Jochen Eisinger]

On Tue, Oct 5, 2010 at 2:57 AM, Sig Weber <siegf...@gmail.com> wrote:

I've verified this twice now and this is AFAIK a new behavior. I've
been testing this on Windows 7 x64 US-English with Chrome 6.0.472.63
and Chromium 7.0.544.0 (downloaded from
http://build.chromium.org/buildbot/snapshots/chromium-rel-xp/).

To track the http requests I've been using the free Fiddler debugging
proxy.

Both browsers do have the same configuration settings applied:

- Scroogle as default search engine (to circumvent the default search
engine ping if "Google" is selected).
- All privacy settings, like the phising and malware protection, are
turned off.
- The home page is set to "New Tab".
- On startup is set to reopen the last pages (which are empty on both
browsers).

When I fire up Chrome it does not ping any Google server (except when
I open the "About" dialog and it runs the check for an update - but
that's expected behavior).

However, when I fire up Chromium it start to issue requests to
clients2.google.com:443 and www.google.com:443 without me doing
anything (not even opening the "Options" dialog).

The request at start-up for clients2.google.com is probably the update check of the extension system. Chrome checks at startup and at regular intervals for extension updates (as mentioned in our privacy policy). You can disable this by not using extensions.

There's a number of possible sources for requests to www.google.com:443. You can go to chrome://net-internals/#events and check what URL Chrome is requesting exactly, then I can help you with that one.

hth

-jochen

 

IMHO this is a regression in Chromium 7 from Chrome 6 I would be glad
if those strange requests could be turned off again (I'm working most
of my time with a 3G connection where I am charged by the KByte which
can become costly when you just have Chromium open with some local
HTML pages).

Cheers,

Sig