Hacker News Reader

Comment by jey | Hacker News Reader

I tried to test my site (NSFW: http://fapseek.com) and got the message "This configuration contains addresses that has been tested too many times the last 24 hours." I assumed someone else had tested the site and that I would be able to test after logging in and verifying ownership of the domain. Even after creating an account, logging in, and creating the loadimpact.txt file, I'm still getting the same error message about my address having already been tested too many times.

View on HN

That's our somewhat restrictive security features that notice some object being loaded as part of your webpage, an object that other sites also use. For example, many sites load urchin.js from google-analytics.com. This means that the daily load our system allows itself to subject google-analytics.com to will quickly be reached. Anyone trying to start a new test for a webpage that loads urchin.js will then be denied to run their test.

We have a list of URLS/sites that are exempted from these checks, but this list needs to be populated. So far we only have a few entries on it (like google-analytics). It seems your site loads things from googleapis.com so I added an exception for that address now. Try again and see if it works.

We probably need to work on the information to users whenever a test is denied also. If you know what the offending URL is, you can remove it from your load script and run the test without it.

yep, loading javascript libraries from CDN is more and more common. I'd suggest you add ajax.googleapis.com and yui.yahooapis.com (there's probably more)

[Edit] you mentioned googleapis.com already.

Thanks, that fixed it. It would be clearer if you included the offending URLs in the error message.

Might want to add Cachefly, too? I think this might be what is stopping me from testing our site, but it doesn't specify so...

I'm getting the same error: http://tlrobinson.net

I have GA, Disqus comments, TipJoy and Reddit badges, and a few other little things.

Maybe you could have an option to restrict it to your own domain name.

Reply on news.ycombinator.com