Re: [Bloat] Adblock - or another extension - is incorrectly blocking the speed test

[jb <justin@dslr.net>]

[-- Attachment #1: Type: text/plain, Size: 1662 bytes --]

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 <jan.ceuleers@gmail.com>
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
>
>

[-- Attachment #2: Type: text/html, Size: 2179 bytes --]