In a refreshingly proactive turn of events, one Amazon AWS abuser replied to me directly. The oggiPlayerLoader.htm 404 errors detailed in my previous web abuse post were courtesy of Oggifinogi, a rich media provider based out of Bellevue, WA.
Directory of Technology Paul Grinchenko emailed me back with a friendly explanation:
We are just looking for our IFRAME buster. You were running at least 1 of our ads in an IFRAME.
No surprise there. We have no prior relationship with Oggifinogi, so I figured their ads had been served through one of the 3rd party ad networks we use (turns out it was ValueClick).
Luckily the issue is simpler than that — Amazon AWS prohibits them from 404-bombing our servers at “an excessive or disruptive rate”. My reply to Paul:
As you probably saw from the “comments” I provided, my complaint was your service’s excessive HEAD requests to the same 6 non-existent files. Judging from the excessively long-term & repetitive 404 errors, it seems your service does nothing useful with the “not found” status code returned by our servers each time. Oggifinogi would be better off using a more responsible system: monitor HTTP response codes to your iframe buster requests, & use that information to limit requests when the files clearly don’t exist. By the way, I somewhat appreciate your service’s HEAD requests versus a full GET, but it’s a bandaid.
Also I urge you to consider Amazon’s advice:
We would strongly recommend that you customize your UserAgent string to include a contact email address so as to allow target sites being crawled to be able to contact you directly.(…although most responsible web services I’ve come across put a URL in their user agent, rather than an email address…)
A few hours later, Paul replied that Oggifinogi does indeed cache iframe buster file presence for a short period, so their requests should not exceed 75 per hour. That fits the profile I saw — no real strain on the web server, but very annoying when tailing error logs.
The good news is Paul agreed to start using a Oggifinogi user agent — hopefully with a help/explanation page URL too.
Paul also sent me the oggiPlayerLoader.htm instructions. Now Oggifinogi can bust our iframes at will, rather than continuing the 404 war. In case anyone else out there wants to join the peace process:
Instructions for Publishers:
- Please download and unpack oggiPlayerLoader.zip – External link for Pubs to Download oggiPlayerLoader.zip
- Make sure that unpacked version is called oggiPlayerLoader.htm
- Copy oggiPlayerLoader.htm to just one of the following locations – single location is enough:
- root of the site – for example: http://www.yoursite.com/oggiPlayerLoader.htm – preferred location
- /oggifinogi – for example: http://www.yoursite.com/oggifinogi/oggiPlayerLoader.htm
- /3rdparty_ad_enablers – for example: http://www.yoursite.com/3rdparty_ad_enablers/oggiPlayerLoader.htm
Please make sure that resulting location is accessible from outside. Location shouldn’t be protected. For example you should be able to open in the browser URL http://www.yoursite.com/oggiPlayerLoader.htm without entering any credentials.
… Working to improving the Interweb, one 404 error at a time.