I think it's the same problem as with php: You could only protect it, when a
HTTP_REFERRER is send (which Netscape does not do):
Assume we have under http://www.quux-corp.de/~quux/ some pages with
inlined GIF graphics. These graphics are nice, so others directly
incorporate them via hyperlinks to their pages. We don't like this
practice because it adds useless traffic to our server.
While we cannot 100% protect the images from inclusion, we can at
least restrict the cases where the browser sends a HTTP Referer header.
PHP General Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]