PROTECTED]
To: CF-Talk [EMAIL PROTECTED]
Sent: Friday, May 24, 2002 7:32 PM
Subject: Re: Emergency: Authorize. net woos
Just to cover the bases, you are using the Relay mode and not Direct
Connect
right? I don't think their new policy cover's ADC...
Unfortunately, the url encoding problem
-Talk [EMAIL PROTECTED]
Sent: Friday, May 24, 2002 9:17 PM
Subject: RE: Emergency: Authorize. net woos
Jon,
You are not alone. :( CFHTTPPARAM was broken in CF v5. They
URLEncodeFormat() the value attribute. Now, in CF v6, they are
url-encoding both the name and value attributes. The solution
I do CFHTTP's with the password passed in and the template is encrypted.
Just adds a little layer of security...
Neil
- Original Message -
From: Jim McAtee [EMAIL PROTECTED]
To: CF-Talk [EMAIL PROTECTED]
Sent: Saturday, May 25, 2002 11:43 AM
Subject: Re: Emergency: Authorize. net woos
-Original Message-
From: James Ang [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 24, 2002 9:17 PM
To: CF-Talk
Subject: RE: Emergency: Authorize. net woos
Jon,
You are not alone. :( CFHTTPPARAM was broken in CF v5. They
URLEncodeFormat() the value attribute. Now, in CF v6, they are
url
On 5/24/02, Dave Watts penned:
Well, that's what you get for listening to me - you can set the Referer
header, but I can't figure a way to stop CF from encoding it, which kind of
makes the header option useless. This is just one of the many, many ways
that CFHTTP stinks - there are so many ways,
On 5/25/02, Mark A. Kruger - CFG penned:
If you are using ADC Direct Response (not relay - direct), the type of
implementation where you get a comma delimited list in return for your post,
then you are not yet required to use the refer URL. Here's a snippet from
the integration doc that Auth.net
- Original Message -
From: Bud [EMAIL PROTECTED]
To: CF-Talk [EMAIL PROTECTED]
Sent: Saturday, May 25, 2002 4:22 AM
Subject: RE: Emergency: Authorize. net woos
On 5/25/02, Mark A. Kruger - CFG penned:
If you are using ADC Direct Response (not relay - direct), the type
On 5/25/02, Jim McAtee penned:
Yes, but if you have any kind of customer support dept doing
credits/refunds, you either have to give everyone the password so that
they can enter it manually, have only trusted personnel do all the
credits, or else store that password in the system anyway. If
Just to cover the bases, you are using the Relay mode and not Direct Connect
right? I don't think their new policy cover's ADC...
Unfortunately, the url encoding problem is one of the worst features of
cfhttp, and has caused me much grief. It makes cfhttp unworkable with some
little
in the butt.
James Ang
Senior Programmer
MedSeek, Inc.
[EMAIL PROTECTED]
-Original Message-
From: Jon Hall [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 24, 2002 4:32 PM
To: CF-Talk
Subject: Re: Emergency: Authorize. net woos
Just to cover the bases, you are using
Alright is there anyone out there that has successfully
implemented the new Authorize. net referer security
reqquirement? I have been trying for two days to do this
with no aval. Dave watts posted something here a couple of
days ago saying that you can pass a httpparam with the type
of
: Friday, May 24, 2002 8:17 PM
To: CF-Talk
Subject: RE: Emergency: Authorize. net woos
Jon,
You are not alone. :( CFHTTPPARAM was broken in CF v5. They
URLEncodeFormat() the value attribute. Now, in CF v6, they are
url-encoding both the name and value attributes. The solution is to use
the appropriate
Tony,
If you are using ADC Direct Response (not relay - direct), the type of
implementation where you get a comma delimited list in return for your post,
then you are not yet required to use the refer URL. Here's a snippet from
the integration doc that Auth.net published.
13 matches
Mail list logo
