Is the problem a browser timeout (ie, not response from the server in
60 seconds) or is PayPal saying the customer is taking too long to
complete the transaction? Many transaction system impose a time limit
for transactions in this way.
I had a similar problem with a WebISO system we wrote. It turns out
that the time on the client's machine was wrong. The year had been set
to 10 years in the past. This caused a time based cookie to be expired
immediately rather than living for the specified amount of time.
If the problem is not an actual browser timeout, I would suspect a time
discrepancy on his machine.
-dirk
On Jun 29, 2004, at 11:41 PM, Robin Darby wrote:
On 29 Jun 2004, at 20:21, Jane wrote:
Folks, never had this problem before.
A customer says he cannot complete a transaction on PayPal due to a
'timeout' before he is through. Others have had no trouble and I see
orders in there for today.
Is this a problem with PayPal or with his own browser? I see orders
in there for today, so others managed to do it.
Hello Jane,
It can be hard to tell, can you get @ the apache error logs??
Is the client using safari, that does have an annoying 60 second
timeout on a single request.
Whenever i do a transactions like that (with paypal or datacash) I
tend to thread/fork the call using methods in the Apache::SubProcess
package (ooh, you are using apache & perl aren't you?).
Thanks
Robin...
_______________________________________________
web-development mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/web-development
Do not post admin requests to the list. They will be ignored.
_______________________________________________
web-development mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/web-development
Do not post admin requests to the list. They will be ignored.
