David, this seems a good idea but in a long user session won't you be left holding a very large list of issued but not used and used validation id's?
I guess once used a validation id can be taken out of the list since a validation criteria is that it be in the list (i.e. have been issued at some point). How, if at all, does SSL play into this (Back=Page Expired?). - Ian Sparks. -----Original Message----- From: david e [mailto:[EMAIL PROTECTED]] Sent: Wednesday, November 27, 2002 11:13 AM To: [EMAIL PROTECTED] Subject: Re: [Webware-discuss] POST Idiom Advice. Always have a hidden field with your forms that has got a random value for "one time" only actions. Generate a suitable number/string and save this to the user session. Then before you perform any actions make sure this value 1) exists, 2) isn't "used", 3) then mark it as used.. Now you should be safe for all kinds of Reloads, Back buttons etc.. Good luck. >This isn't a webware question per-se but I'd like to ask how people >handle POST's. > > >The problem for me is the Browser Refresh button. If you click it >now its not going to do what it says ("Refresh"), its going to >re-post the delete action (which could be bad). ------------------------------------------------------- This SF.net email is sponsored by: Get the new Palm Tungsten T handheld. Power & Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss ------------------------------------------------------- This SF.net email is sponsored by: Get the new Palm Tungsten T handheld. Power & Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
