On 30 July 2004 16:25, Ashley M. Kirchner wrote:
> Jason Barnett wrote:
>
> Though I'm intrigued by two things: a) why am I getting both
> $_REQUEST as well as $_POST variables
Because $_REQUEST is an aggregate of $_GET, $_POST and $_COOKIE. That's the way it's
defined: see
http://www.php
Jason Barnett wrote:
Is there a question here? Or is this a resolution?
Thanks for asking. I found a solution that works. Basically when
data gets returned, check the unique id against the DB. If it doesn't
exist, insert it together with the other stuff I want in the DB. If it
does, don'
Is there a question here? Or is this a resolution?
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
On Thu, 29 Jul 2004, Skippy wrote:
ATTENTION: if you receive the PayPal data by POST be sure to redirect
using "303 See Other", which will "deactivate" the POST and force the
redirect to use GET. Of course, forwarding any data to the 2nd script
should be done as GET parameters.
I stuck phpinfo(
>
> PayPal passes a ton of data back to us when someone's done
> purchasing something. I use some of that information and shove it all
> into a database. Problem is, if someone hits reload on their browser, I
> get the same data re-inserted again. Reload the page four times, and I
> will get
Quoting "Ashley M. Kirchner" <[EMAIL PROTECTED]>:
> PayPal passes a ton of data back to us when someone's done
> purchasing something. I use some of that information and shove it all
> into a database. Problem is, if someone hits reload on their browser, I
> get the same data re-inserted a
* Thus wrote Ashley M. Kirchner:
>
>PayPal passes a ton of data back to us when someone's done
> purchasing something. I use some of that information and shove it all
> into a database. Problem is, if someone hits reload on their browser, I
> get the same data re-inserted again. Reload t
7 matches
Mail list logo
