From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mailrelay116.isp.belgacom.be (mailrelay116.isp.belgacom.be [195.238.20.143]) by huchra.bufferbloat.net (Postfix) with ESMTP id 3115321F210 for ; Sat, 25 Apr 2015 23:28:18 -0700 (PDT) X-Belgacom-Dynamic: yes X-Cloudmark-SP-Filtered: true X-Cloudmark-SP-Result: v=1.1 cv=Ax9Kd9og7W2htzcJF9odWb+87PP6pPoG1t8Q07ebhfo= c=1 sm=2 a=tJe01QhAHdwA:10 a=IkcTkHD0fZMA:10 a=xQ-PNo_hQonC9mSc9cgA:9 a=QEXdDO2ut3YA:10 a=BiEOe0-q434XoFlX:21 a=B3N5N5pfF4cBb2s2:21 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A2BmBgA+hDxV/zaA9FFcgwyEScMOhHmCXQKBKjoTAQEBAQEBAYEKhCEBAQQjMwYcEQsLDQICBRYLAgIJAwIBAgERFh4GAQwIAQGIEgEYAbIQgWuLPwoZgQmEbAEBCAEBAQEegSGKF4UMgmiBRQEEnA6BIoYXiliDUCOCOIE+PIJ1AQEB Received: from 54.128-244-81.adsl-dyn.isp.belgacom.be (HELO zotac.xperim.be) ([81.244.128.54]) by relay.skynet.be with ESMTP; 26 Apr 2015 08:28:18 +0200 Received: from [192.168.1.172] (mordor.xperim.be [192.168.1.172]) by zotac.xperim.be (8.14.4/8.14.4/Debian-2ubuntu2.1) with ESMTP id t3Q6Q6eF018683; Sun, 26 Apr 2015 08:26:06 +0200 Message-ID: <553C84FE.5070101@gmail.com> Date: Sun, 26 Apr 2015 08:26:06 +0200 From: Jan Ceuleers User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: jb , bloat References: <553B2863.2020600@gmail.com> <553BA193.1030907@gmail.com> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [Bloat] Adblock - or another extension - is incorrectly blocking the speed test X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Apr 2015 06:28:48 -0000 On 26/04/15 06:17, jb wrote: > The warning is correct in that it is probably NOSCRIPT. I think. > All the speed test knows is that an API call to all servers was brutally > failed > in an unexpected way. There is no visibility into what caused the > failure, only > that it should not occur in a clean browser. If you open the console > you can probably see more than the javascript gets told. Hi Justin, I think the problem is that you may be referring to the test servers by IP address rather than by DNS names. Here is why I think that: I picked Noscript's "disable everywhere" option, then successfully ran the test. I was then able to see in Noscript which sites were running scripts and saw a number of IP addresses among them. I then added these IP addresses to the whitelist, re-enabled Noscript and verified that I was able to still run the test. If you are able to put all of these servers in a DNS domain under your control then a single whitelist entry in Noscript would make them all work, and not just the ones that are being picked at my location. By the way: I then re-enabled Adblock and was still able to run the test. So I recommend blaming Noscript in the error message rather than Adblock (and then perhaps also mentioning the whitelist rule that fixes it). Thanks, Jan