If using IIS, use an ISAPI filter on the images dir to check that the referrer is from an authorised host. A similar arrangement is available for Apache but is far easier to implement, though I forget the details right now.
Steve > -----Original Message----- > From: Taz [mailto:[EMAIL PROTECTED] > Sent: 21 January 2004 09:38 > To: [EMAIL PROTECTED] > Subject: Re: [ cf-dev ] OT: preventing hotlinking > > > I've just thought of an interesting solution to this problem, > that doesn't > require more 3rd party plugins for IIS. > > Assuming your application is CF throughout, you could store > the name of the > images directory in a database and pick this up for output in > any links. > Then you could set up a session to change the name of the > images directory > every day. > > This wouldn't physically stop people from linking to images, > but it would > make their links redundant every day. > > Taz > > > -- > ** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/ > > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > For human help, e-mail: [EMAIL PROTECTED] > > -- ** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] For human help, e-mail: [EMAIL PROTECTED]
