Well said, glad you agree with me. :o) Just asking about bots cause until recently, I hadn't considered them a *potential* risk (perhaps not so much a risk as a bit of a pest). Looks like robots.txt is the answer.
Cheers, D -----Original Message----- From: Taz -=TT=- [mailto:chris@;cfmaster.co.uk] Sent: 17 October 2002 10:53 To: [EMAIL PROTECTED] Subject: Re: [ cf-dev ] Locking error on DB >> What do you mean by 'potentially damaging script'? > basically anything that makes a change on the server. > So data access is ok, but data updates could be damaging if run unintentionally. Strictly speaking, there shouldn't be such templates in any site. Anything that does instert/update/delete ops on a database table should be locked down tight. Not just because of bots, but to stop potential hackers too. Preventative measures are best on any software app. If you're expecting certain values and datatypes for a database op, make sure that those values are a. present b. valid c. not potentially damaging if not, spit out an error message As for stopping robots, the easiest way of stopping them accessing pages is to enter those paths into the robots.txt file. 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]
