Forum Moderators: open
So, are most browsers programmed to treat the page as the refferrer for an image file that is called by a relative link in the page code, or do some make direct requests? Or have I got the wrong end of the stick?
Jocelyn
I don't want people who use download tools like FlashGet or HTTrack to just be able to rip the site in a few minutes. Too much time and effort and a little bit of money went into developing the images and in my industry thieving of other sites product pics is commonplace. However if a lot of honest people are just seeing broken image links then I'll have to rethink it.
This is one example from today:
67.80.135.145 - - [25/Mar/2003:08:50:30 -0800] "GET /Assets/images/picture.jpg HTTP/1.1" 403 243 "-" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; {Cablevision Systems Corporation})"
This visitor got nothing but 403s for images. All requests, including html and css files were direct, no referrer. I'm wondering if his browser is making the 'wrong' kind of request (or as you say he has disabled referrers) or is he actually trying to whack the site?