Hi Pounders I just want to share something that is obvious now, but not since deploying pound.
Have being using pound as a HTTPS front end for eCommerce transactions. A fraction of users have complained about experiencing 'An internal server error occurred' message when processing credit card information. Additionally I couldn't replicate it on demand. Unfortunately the payment gateway can take some time processing payments, and by default pound will timeout backend connections greater then 15 seconds. Below are the giveaway error messages with the virtually consistent timeout values: Apr 17 22:26:53 host pound: (b7275b90) e500 response error read from 127.0.0.1:80/POST /snip HTTP/1.1: Connection timed out (15.001 secs) Apr 17 22:29:28 host pound: (b7275b90) e500 response error read from 127.0.0.1:80/POST /snip HTTP/1.1: Connection timed out (14.999 secs) So the moral of the story is the increase default TimeOut directive to greater then 15 seconds. Your payment gateway provider will likely advice you how long a transaction can take. -- Simon Males -- To unsubscribe send an email with subject unsubscribe to [email protected]. Please contact [email protected] for questions.
