Try it without the URLEncodedFormat, we had a similar problem when migrating over.. What's happening is cfhttparam is encoding it automatically, and hense your ddata is double encoded.
Nat -----Original Message----- From: Trey Rouse [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 12, 2002 1:36 PM To: CF-Talk Subject: CFhttp problems between 4.5.1 and 5.0 AND working with PayPal IPN Has anyone experienced any problems using CFHTTP in 5.0? This may be an old question, but I'm definitely experiencing a problem with code that works in 4.5.1 and fails in 5.0. Here is a snippet: <CFSET str="_notify-validate"> <CFLOOP INDEX="TheField" list="#Form.FieldNames#"> <CFSET str = str & "&#LCase(TheField)#=#URLEncodedFormat(Evaluate(TheField))#"> </CFLOOP> <cfhttp url="https://www.paypal.com/cgi-bin/webscr"; method="POST" resolveurl="false"> <cfhttpparam type="FORMFIELD" name="cmd" value="#str#"> </CFHTTP> Those of you familiar with the Paypal IPN will recognize this code as almost exactly from their provided example. What I'm finding is on 4.5.1 the http post is being received by paypal correctly. However on 5.0 the first field, cmd=_notify-validate, is not being recognized by their server. Anyone have any similar experiences or a work around? I'm curious if anyone on list has written any code on a 5.0 server that interfaces with the paypal instant payment notification process? Thanks Trey Rouse ______________________________________________________________________ Get Your Own Dedicated Windows 2000 Server PIII 800 / 256 MB RAM / 40 GB HD / 20 GB MO/XFER Instant Activation � $99/Month � Free Setup http://www.pennyhost.com/redirect.cfm?adcode=coldfusionb FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
