- From: David Woolley <david@djwhome.demon.co.uk>
- Date: Fri, 20 Dec 2002 20:57:58 +0000 (GMT)
- To: w3c-wai-ig@w3.org
> Could not this problem be dealt with by simply checking the referer page > and if there referer field was not CAST (or, now WatchFire) either > reject the request, or throttle back the service? No. Anyone scripting a service like this is quite capable of forging the Referer. They are probably already forging the User Agent. It's unlikely that they obey the robots protocol. Rejecting on Referer may cause some accessibility problems, as some proxies suppress it for privacy reasons.
Received on Saturday, 21 December 2002 06:04:32 UTC