-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sat, Oct 08, 2016 at 11:35:21AM -0400, Tony Baldwin wrote:
[...] > >Can you use the chrome developper tools to see what's going on ? (Press > >the F12 key while chrome is open) Select the network tab, and type the > >url in your address bar. > >The network panel should show you what happens > > That doesn't seem to tell me anything traceroute doesn't, except > trqacerout doesn't get redirect to a Yahoo! search like chrome does, > but nothing I see there seems ot clarify WHY or HOW it's getting > redirected, it's just showing me that it IS being led though some > circolocuitous route to where it should not. A shot in the dark, but worth a try anyway: IPV4 vs IPV6? But I'd rather suspect Chrome doing something weird to the URL before resolving (or -- who knows! having its own built-in resolver). Perhaps looking at the traffic with tcpdump/wireshark can give you an idea. Regards - -- tomás -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlf5NeoACgkQBcgs9XrR2kZ+PQCeOsGFniEXtN/uNxh7xpHmc5jg SG0AmgMz751oR58+BwBJEKN5RP60UsGK =NsR2 -----END PGP SIGNATURE-----
