Hi, With the same version 6.0.472.63~r59945-2 I'm not seeing this problem.
My best guess would be that the submitter had an HTTP proxy server configured or something? And it was the proxy server that may have had the issue. Proxy exceptions are enabled by default in chromium-browser for 'localhost' and '127.0.0.0/8', but not for the IPv6 equivalents 'ip6-localhost' or '::1/128'. In fact IPv6 addresses must be given in square brackets in the proxy exception list or they're ignored. Maybe the issue was even with whatever web service the submitter was running on the IPv6 loopback interface. (And maybe the other browser the submitter tried, was connecting via a proxy that was allowing connections to a working server on that host's loopback interface instead). If the submitter finds a way to reproduce this again, it may help to expand with the [+] button the full error message on the "This webpage is not available" page. Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
