RE: Re-Send: Preventing "Cou-pon" Generation Fraud.

2006-03-13 Thread Che Vilnonis
using Point #1 above would solve this problem as well. :) ~Che -Original Message- From: Bryan Stevenson [mailto:[EMAIL PROTECTED] Sent: Monday, March 13, 2006 2:08 PM To: CF-Talk Subject: Re: Re-Send: Preventing "Cou-pon" Generation Fraud. 1st...it's coupon and not cou-po

Re: Re-Send: Preventing "Cou-pon" Generation Fraud.

2006-03-13 Thread Deanna Schneider
Well, you could eliminate worrying about that by storing the 5 email addresses that are sent, then checking to see if they've reached their quota for the order. On 3/13/06, Che Vilnonis <[EMAIL PROTECTED]> wrote: > > I sent this before I did not even get a copy sent to myself. Perhaps it > was > c

Re-Send: Preventing "Cou-pon" Generation Fraud.

2006-03-13 Thread Che Vilnonis
I sent this before I did not even get a copy sent to myself. Perhaps it was considered junkmail? Thus, the misspelling. See below. -- Preventing "Cou-pon" Generation Fraud. I am developing an e-commerce site that presents customers with an opportunity to send five dollar cou-pons to thei

RE: Re-Send: Preventing "Cou-pon" Generation Fraud.

2006-03-13 Thread Che Vilnonis
True. I appreciate all the help I can get though. :) -Original Message- From: Bryan Stevenson [mailto:[EMAIL PROTECTED] Sent: Monday, March 13, 2006 2:36 PM To: CF-Talk Subject: Re: Re-Send: Preventing "Cou-pon" Generation Fraud. > #1. Ding, ding, ding. We have a winner!

RE: Re-Send: Preventing "Cou-pon" Generation Fraud.

2006-03-13 Thread Ian Skinner
I believe one answer is to generate a key on the server and then pass that key to the client. 5 coupons per key and its all used up. Now the logic on when and how a key is generated is dependant on the application. I suspect since you have users there is some kind of key associated with them.

Re: Re-Send: Preventing "Cou-pon" Generation Fraud.

2006-03-13 Thread Bryan Stevenson
> #1. Ding, ding, ding. We have a winner! Bryan, that's the easiest way to do > it. > #2. Bryan, what I am talking about is the "save as" feature in the browser. > The form is copied to the desktop, it is double clicked (and maybe edited) > and then resubmitted. But, I would imagine, that using Poi

Re: Re-Send: Preventing "Cou-pon" Generation Fraud.

2006-03-13 Thread Greg Morphis
h 13, 2006 1:58 PM > To: CF-Talk > Subject: Re-Send: Preventing "Cou-pon" Generation Fraud. > > I sent this before I did not even get a copy sent to myself. Perhaps it > was considered junkmail? Thus, the misspelling. See below. > > -- > > Preventin

RE: Re-Send: Preventing "Cou-pon" Generation Fraud.

2006-03-13 Thread Che Vilnonis
Would that make more sense? ~Che. -Original Message- From: Katz, Dov B (IT) [mailto:[EMAIL PROTECTED] Sent: Monday, March 13, 2006 2:04 PM To: CF-Talk Subject: RE: Re-Send: Preventing "Cou-pon" Generation Fraud. 1) You can set a session variable or client variable to say "

Re: Re-Send: Preventing "Cou-pon" Generation Fraud.

2006-03-13 Thread Bryan Stevenson
1st...it's coupon and not cou-pon ;-) > #1. How do I stop the customer from hitting the "back" button to resubmit > the form again? Namely, how do I stop the same set (or a different set) of > emails from receiving these cou-pons? I realize the "back" button issue has > come up in various incarnat

RE: Re-Send: Preventing "Cou-pon" Generation Fraud.

2006-03-13 Thread Katz, Dov B \(IT\)
ent to get around both of these, but would someone go through all the trouble to get discounts for your site? dov -Original Message- From: Che Vilnonis [mailto:[EMAIL PROTECTED] Sent: Monday, March 13, 2006 1:58 PM To: CF-Talk Subject: Re-Send: Preventing "Cou-pon" Generation