That's a feature of Chrome.
In NetMon, you won't see the attempts to connect to the random
hostnames, instead you'll see three failed DNS lookups for three
random hostnames.
Chrome does this to attempt to determine whether the user is behind an
ISP/network environment that hijacks DNS lookup failures and returns
bogus records that point to the ISP's search pages (for which the ISP
gets advertising money). Chrome needs to do this in order for their
"Hey, this address doesn't exist so do a google search" feature to
work properly and not get confused by the bogus DNS records.
When you have a proxy in place (for example, Fiddler) Chrome does the
same sort of thing but with a GET (since it's the proxy's job to do
the DNS lookup, but the browser must actually make a HTTP request for
the DNS request to happen).
-Eric
On Jun 20, 6:45 am, rjsargeant <
richard.sarge...@gmail.com> wrote:
> Hi,
>
> When I start Google Chrome, Fidder shows three consecutive 502 errors
> immediately after the 'CONNECTwww.google.com:443'command. The