in reply to Re: SOAP::Transport::HTTP::Client::send_receive: 500 Can't connect to testproxy:8080
in thread SOAP::Transport::HTTP::Client::send_receive: 500 Can't connect to testproxy:8080

Thanks for the response. We have checked with service-now team. Nothing has been changed from their end. We have observed that in RHEL 6.9, the perl-libwww package has been updated to perl-libwww-perl-5.833-5. With this update LWP also updated. I am trying to run simple script to connect service-now and get records. Here is my code 
#!/usr/bin/perl -w
use SOAP::Lite;
use Data::Dumper;
use Getopt::Long;
use strict;
use warnings;
$ENV{https_proxy} = "http://myproxy.com:8080"; 
$ENV{HTTPS_PROXY} = "http://myproxy.com:8080"; 

sub SOAP::Transport::HTTP::Client::get_basic_credentials {
        return "k2soap" => "REDACTED"; #PROD
}
my $soap = SOAP::Lite -> proxy('https://usr_soap:pwd_soap@swe.service-
+now.com/change_request.do?SOAP');

my $method = SOAP::Data->name('getRecords') ->attr({xmlns => 'https://
+www.service-now.com/'});

my @params = (
         SOAP::Data->name(number => $ARGV[0])
);
print "Searching for Change Request... $soap and $method\n";
my $result = $soap->call($method => @params);

[download]
We are receiving below error when we run script 500 handshakefailed at soap_connection.pl line 18. Could you please help on this error.
  • Comment on Re^2: SOAP::Transport::HTTP::Client::send_receive: 500 Can't connect to testproxy:8080
  • Download Code

Replies are listed 'Best First'.
Re^3: SOAP::Transport::HTTP::Client::send_receive: 500 Can't connect to testproxy:8080
by NetWallah (Canon) on Jun 13, 2018 at 20:45 UTC
    This code looks incorrect: 
    my $method = SOAP::Data->name('getRecords') ->att...

    [download]
    In order to "get" the "name", you need an existing SOAP::Data object.
    I don't know what accessing that as a class method will get you.

    You should try to error check that .. as a minimum, ensure that $method is not undef.

    Error 500 is still a server-side error - so server-side web-server logs can also help identify the cause.

    If you can reproduce this problem using a 'curl' command, it may be easier to convince the server support people that the issue is on their side.

                    Memory fault   --   brain fried

[reply]
[d/l]
[reply]

In Section Seekers of Perl Wisdom