Re: best way to limit # of attempts to login to protected page?
This WebDNA talk-list message is from 2000
It keeps the original formatting.
numero = 35430
interpreted = N
texte = The way I do it is, pass a variable(counter) and each time increment it, when it gets to a certain value, then you know what to do...========================================================== _O_/\NUP Setty / | \/ERTical Net / \ http://www.vertical.net _\ \_ 336-218-8562 Ext. 218 o o o o ========================================================== ----- Original Message ----- From: John Butler
To: WebCatalog Talk Sent: Saturday, July 29, 2000 10:06 PM Subject: best way to limit # of attempts to login to protected page? > If I want to restrict the number of times someone can attempt to login > to a protected page, what is the best way? > > ...update a db field (with an incrementally counting number: +1 for > every attempt) in a record whose key field is their IPADDRESS? And when > it hits the threshhold # then disallow that IP from trying again? Then > use a trigger to delete records older than (24) hours... > > ? > > > ------------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > To switch to the DIGEST mode, E-mail to > Web Archive of this list is at: http://search.smithmicro.com/ ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/
Associated Messages, from the most recent to the oldest:
The way I do it is, pass a variable(counter) and each time increment it, when it gets to a certain value, then you know what to do...========================================================== _O_/\NUP Setty / | \/ERTical Net / \ http://www.vertical.net _\ \_ 336-218-8562 Ext. 218 o o o o ========================================================== ----- Original Message ----- From: John Butler To: WebCatalog Talk Sent: Saturday, July 29, 2000 10:06 PM Subject: best way to limit # of attempts to login to protected page? > If I want to restrict the number of times someone can attempt to login > to a protected page, what is the best way? > > ...update a db field (with an incrementally counting number: +1 for > every attempt) in a record whose key field is their IPADDRESS? And when > it hits the threshhold # then disallow that IP from trying again? Then > use a trigger to delete records older than (24) hours... > > ? > > > ------------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > To switch to the DIGEST mode, E-mail to > Web Archive of this list is at: http://search.smithmicro.com/ ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/
Anup Setty
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
date format (2000)
WCS Newbie question (1997)
Convertchars Problem (2004)
Document Contains No Data! (1997)
Next X hits (1996)
Re1000002: Setting up shop (1997)
ShowNext for method=POST (1997)
Web Catalog vs. ICAT (1997)
RE: Signal Raised (1997)
[WebDNA] Triggers not working (2011)
Deleting Orders (1997)
SandBox and ImageMagick (2003)
WebDNA DHTML Newsticker 1.01 released (2003)
Fun with Dates - any progress? (1997)
emailer don't work (1998)
Pithy questions on webcommerce & siteedit (1997)
Shop till you drop dead on the avenue ... (1997)
The IBC root beer has arrived! (1997)
FYI-AuthorizeNet-possible downtime (2001)
Replacing entry (1998)