Re: Debugging LWP

Well, I tried adding the code. Now my script has this at the top:

use Strict;
use LWP 5.803;
use LWP::Debug qw(+);
use HTTP::Request::Common qw( POST );
[download]

But, I still receive a CGI Timeout: The specified CGI application exceeded the allowed time for processing. The server has deleted the process. This script is for a well known transaction, Authorize.net's AIM CC Transactioning. I do CC processing in 5 different scripts, all which don't work anymore. I can transact CC's still though, so I know my account is active. The path to Authorize.net is working. I contacted them first. I even downloaded their test Perl script. Didn't work, and it's all coded and ready to run a test transaction. Worst case, if it was Authorize.net, I would receive an error. Any other ideas? Why did the LWP::Debug not report an error? Thanks for all your help in advance. I just started this business, and not being able to process credit cards will kill it. If this is an issue with my hoster, any ideas why? Tom

Comment on Re: Debugging LWP Download Code

Replies are listed 'Best First'.
Re^2: Debugging LWP by vladb (Vicar) on Feb 11, 2006 at 18:18 UTC
If the host is telling you they have registered a hit from your script, are they able to send you any log of that request? I would specifically look for any error messages etc. Try sending a POST request via the system telnet utility to eliminate your script entirely. _____________________ "We've all heard that a million monkeys banging on a million typewriters will eventually reproduce the entire works of Shakespeare. Now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California	[reply]
Re^3: Debugging LWP by tdrought (Novice) on Feb 11, 2006 at 19:22 UTC
I am running this script from a hosted Windows server. So I cannot run a telnet. But, what I just did was bring the script to my local machine which has IIS and ActivePerl installed. Install the SSLeay and tested the script locally. It ran just fine which tells me it's the hosters server which is causing the problem. I am going to call them now. Hopefully, they can get to the bottom of this, else I will have to switch servers.	[reply]
Re^4: Debugging LWP by renodino (Curate) on Feb 12, 2006 at 00:45 UTC
(Longshot guess, but I've been burned by this in the past too) Have you tried connecting via a numeric IP address ? Windows has been known to have some nasty resolver caching behaviors which, if not registry hacked properly, can cause it to hang onto a bad DNS resolution for a long time...so if your target has changed its IP address recently, the Windows resolver cache may not have flushed yet. Here's the story wrt WinXP...	[reply]