Thanks,
Finally got the bugs out of my head. The easiest way to do the post-
back in order is <@CGIPARAM> rather than mucking with any POSTARGs.
But the bigger problem was that I was testing in the paypal sandbox,
but posting back to paypal. DOH!
On Mar 15, 2006, at 4:59 PM, Jason Schulz wrote:
Bill,
Page 56 of O'Reilly's HTTP: The Definitive Guide has a nice little
diagram of this.
A results action that contains a request$httpheader followed by a
blank line, followed by each of your arguments on a new line (or
<@crlf> separated) in your preferred order would do.
You would need to define request$httpheader, but that isn't hard.
Regards,
Jason.
On 15/03/2006, at 9:51 AM, William M Conlon wrote:
The packet analyser shows my post back is now the same as what
paypal sends me, except for the order of the arguments. Does
anyone know how I can get them in actual order?
WITH IMAGINATION
Planning, Implementation and Management of Web Applications
160 Pacific Highway North Sydney NSW Australia 2060
phone + 612 9929 9229 fax + 612 9460 4770
web - www.wi.com.au email - [EMAIL PROTECTED]
______________________________________________________________________
__ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
Bill
William M. Conlon, P.E., Ph.D.
To the Point
345 California Avenue Suite 2
Palo Alto, CA 94306
vox: 650.327.2175 (direct)
fax: 650.329.8335
mobile: 650.906.9929
e-mail: mailto:[EMAIL PROTECTED]
web: http://www.tothept.com
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
