At 10:22 AM 7/26/00 -0400, John Young wrote: >Declan's article ran on Friday July 21 day and the hits from it did not >seem to affect the sites. Saturday, an AP story appeared but it did not >include links to the site, however, Drudge Report picked up the AP story >and provided a munged link to jya.com: > > http://jya.com/crypto.htmhttp://jya.com/crypto.htm > >Thousands of hits on this non-existent file began to appear in the >error log, and there have now been tens of thousands of them (maybe in >the hundreds of thousands, no count has been made, and each is >multiplied by Digital Nation's error page with its graphics). You should be able to fix this quickly - GO CREATE THE FILE! Make it a pointer to the real thing or some mirror, and make sure it's got no graphics content. (I checked to see whether you've done so already, but you're overloaded so I can't tell.) >We would appreciate advice on whether these log entries and messages are >consistent with simple overloading or could indicate an attack, even a >presumbably accidental attack by Drudge (who has still not answered my >Saturday e-mail to correct the URL). The classic way people deal with situations like this (i.e. the last 6-12 months) is to either rent space at a bigger ISP, or deal with a caching-service vendor like Akamai, Sandpiper, or AT&T who will cache your pages on their big-pipe cache engines and play whatever DNS or HTML games you need to point to them. (One popular approach is to use the annoying HTML redirect stuff; another is to serve the text page yourself with the IMG references pointing to that cache servers. You can also have your DNS point to them first if you prefer.) But you'll be charged by the megabyte shipped, or the hit, or the 95th percentile of the bit rate, or some similar pricing. There are some cheap-ass ways to mirror your pages as well. One is to use a big free web-page server like Geocities, and spread your web pages' images around there, and point your HTML to them, so again you're only serving part of the material yourself. Another is to make sure the pages are searched for by Google, a search engine which keeps a cached copy of the pages it finds as well as pointing you to the (often changed original), and then point users to the Google cache instead of your own page. If you're getting hit because of Slashdot, contact the /. administrators and bug them to either cache your stuff or at least point to some URL at a high-capacity site. /. doesn't currently cache, because back when they were an amateur-run business, they didn't want to pay lawyers to decide for them when caching was a copyright agreement people would sue you for and when it was a public service, and they've never updated that policy now that they're a real business with real lawyers. It also takes some work, but not really very much for them. Thanks! Bill Bill Stewart, [EMAIL PROTECTED] PGP Fingerprint D454 E202 CBC8 40BF 3C85 B884 0ABE 4639
