> Now I see the problem! Is disallowing it through robots.txt to draconian?
Not for some dubious search engines which don't say who they are... ;) (And I've had one which didn't take no for an answer, now care of apache's rewrite engine.) But in general, one doesn't want to cut off search engines altogether, but as it's all non-interactive machine-only traffic, the lowest priority seems to be adequate to me. This is home sites here, which don't have any priority anyway, not big commercial sites where restricting bandwidth is counterproductive. For the record, http://modules.apache.org/ seems to list everything there is. There isn't a universally useful bandwidth limiting tool for apache 2 (don't know about 1.3), and the choice is between the 3 I posted. Perhaps there are bandwidth-shaping transparent proxies. Using a packet filter for shaping restricts conditions to the tcp parameters, and the http headers are out of reach there. Thanks to CF and his horse btw, great tool for testing! Volker -- Volker Kuhlmann is possibly list0570 with the domain in header http://volker.dnsalias.net/ Please do not CC list postings to me.
