From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ig0-x236.google.com (mail-ig0-x236.google.com [IPv6:2607:f8b0:4001:c05::236]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 611E221F23B for ; Sun, 26 Apr 2015 07:17:33 -0700 (PDT) Received: by igbhj9 with SMTP id hj9so45076749igb.1 for ; Sun, 26 Apr 2015 07:17:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=2ZAw/UW2ufAAtcLnH0wuobPxO/1OlfLhlQt508UYGNI=; b=QkkIR00H7SYzMHuNE9VlZswvicQzVnyMFxd3qrwVl3x1PCQC5XAPTA2/Q57Gx04SMj r1BELIOOsnU+cRDi0hRIRAyWsOcEHkuOjV5vOejYYlLaPaTDOCzoTUOthvkXi5/M0VJD KsQXbP7i4KBXf+K12flaNZ9ZLy2scsy/W0OPimg1AtQhoKEby+h7uzRvNR0z8tQdyyoc 9Fk76tiZNc+taxk6EWi2GkEVotpzq8Ns5uFLQr3CvhwWrFEBWtz2Ty/wF2Iyp2DTkUjQ ukfteETkGF8348XQQALe2+ubVPQqfn0OtautPiEIl/to2p+ezn/qp3lNN8uul0QnYoG+ bBfQ== MIME-Version: 1.0 X-Received: by 10.50.109.138 with SMTP id hs10mr8323198igb.48.1430057849661; Sun, 26 Apr 2015 07:17:29 -0700 (PDT) Sender: justinbeech@gmail.com Received: by 10.50.107.42 with HTTP; Sun, 26 Apr 2015 07:17:29 -0700 (PDT) In-Reply-To: <553C84FE.5070101@gmail.com> References: <553B2863.2020600@gmail.com> <553BA193.1030907@gmail.com> <553C84FE.5070101@gmail.com> Date: Mon, 27 Apr 2015 00:17:29 +1000 X-Google-Sender-Auth: OSDYo_RVL1MOkWLCV5EfcbLyAk0 Message-ID: From: jb To: Jan Ceuleers , bloat Content-Type: multipart/alternative; boundary=089e0122e6aa2358260514a14a2b 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 14:18:09 -0000 --089e0122e6aa2358260514a14a2b Content-Type: text/plain; charset=UTF-8 And please excuse the rant. It is not directed at you personally. I've been through this several times on-site, and tried my luck being friendly to the noscript developer, and I'm sort of done. You would not have known that. On Sun, Apr 26, 2015 at 4:26 PM, Jan Ceuleers wrote: > 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 > > --089e0122e6aa2358260514a14a2b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
And please excuse the rant. It is not directed at you pers= onally.

I've been through this several times on-site, and = tried my luck
being friendly to the noscript developer, and I'= ;m sort of done.
You would not have known that.


On Sun, Apr 26, 2015 at 4:26 PM, Jan Ceuleers <jan.ceuleers@gmail.c= om> wrote:
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 brutal= ly
> 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 success= fully 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


--089e0122e6aa2358260514a14a2b--