Maybe use cookies? In other words, get and set cookies on the site, and the software *may* not be able to handle the fact that cookies are being used...?
Also could use session management in a similar way... Following on from that... another way around it is to obfuscate the URL so that the end user doesn't notice, but so that it forces scraping software to use the obfuscated URL each time... Makes it harder to scrape, but again, not impossible. Erm... Or just use a flash interface...? ;) Other thing to note is what browser is being used. Easy to get round I know, but if you know which browser, you could set some browser specific javascript to let the site know that it's the correct browser and only show the content if that javascript works...? All from the top of my head (and I'm quite tired this Monday so if any of these ideas are not quite all there, then ignore them!) Paul > -----Original Message----- > From: Peter Dray [mailto:[EMAIL PROTECTED] > Sent: 15 September 2003 11:58 > To: [EMAIL PROTECTED] > Subject: [ cf-dev ] Stopping 'db scrapes' > > > People, > > One of the sites I am working on gets its data 'scraped' for > use in a piece of software developed by a competitor. They > use an http get or post from an end users machine so it's > impossible to tell the software apart from any other user. > > Has anyone here any advice on what methods to use to defeat > this sort of thing? > > Cheers > > Pete Dray > > > -- > ** 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]
