I have found the 5.5 version of <@url> to work much better, and be
less buggy.
As a thought, are you sending post as an array, or as a postarg
string. If one doesn't work, maybe the other? or maybe a SPACE after
the equal? might throw an error, might not.
--
Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
ph: 530.645.4040 x222 fax: 530.645.4040
[EMAIL PROTECTED] - [EMAIL PROTECTED]
http://bighead.net/ - http://eventpix.com/
On Mar 10, 2006, at 7:39 PM, William M Conlon wrote:
I'm having a hard time getting Paypal Instant Payment Notification
to validate.
The process requires me to post-back to Paypal the same data that
they posted to me. I'm using Bryan Hughes' paypal_notify.taf as a
prototype, but I can't get Paypal to respond to my POST-back with a
'Verified' answer. I always get an 'Invalid' answer.
I've investigate by running the same post-back to paypal and to my
witango server. This shows that there is indeed a difference in
the POST arguments! Apparently witango 5.0.1.065 <@URL> is not
POSTING an argument with a NULL value. So where Paypal sends me
<snip>
charset=windows-1252
custom=
first_name=William
</snip>
Witango posts back:
<snip>
charset=windows-1252
first_name=William
</snip>
The debug trace shows that the custom variable is indeed in the
post argument array:
10/03/2006 19:17:04 66.135.197.164
[EMAIL PROTECTED] -1470862416 1
97 [Changed Vars] request$postarg_array[11,1]=custom;
request$postarg_array[11,2]=;
Has anyone resolved this?
Do I have to generate the entire HTTP post myself instead of using
<@URL>?
Bill
______________________________________________________________________
__
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
