in reply to Re^2: XML Parsing issue with SOAP::Lite (xml declaration)
in thread XML Parsing issue with SOAP::Lite (xml declaration)

If you get Client-Warning: Internal response, then LWP never talked to the remote server.

So, there is an issue that A.B.C.D does not listen on 8443 from your host. Maybe you need a proxy.

I would first debug the TCP connection from the client to the server on port 8443, by trying with another HTTP client like wget or curl.

Replies are listed 'Best First'.
Re^4: XML Parsing issue with SOAP::Lite (xml declaration)
by erwanhumez (Novice) on Mar 10, 2017 at 11:32 UTC
    I already checked that HTTPs connection which seems fine and i do get quite some payload back from the server: 
    11:26:39.563856 IP clientserver.55766 > A.B.C.D.pcsync-https: Flags [S
+], seq 1975907677, win 29200, options [mss 1460,sackOK,TS val 2401372
+060 ecr 0,nop,wscale 7], length 0
11:26:39.564017 IP A.B.C.D.pcsync-https > clientserver.55766: Flags [S
+.], seq 3050450316, ack 1975907678, win 14480, options [mss 1460,sack
+OK,TS val 561024198 ecr 2401372060,nop,wscale 7], length 0
11:26:39.564041 IP clientserver.55766 > A.B.C.D.pcsync-https: Flags [.
+], ack 1, win 229, options [nop,nop,TS val 2401372061 ecr 561024198],
+ length 0
11:26:39.564174 IP clientserver.55766 > A.B.C.D.pcsync-https: Flags [P
+.], seq 1:248, ack 1, win 229, options [nop,nop,TS val 2401372061 ecr
+ 561024198], length 247
11:26:39.564274 IP A.B.C.D.pcsync-https > clientserver.55766: Flags [.
+], ack 248, win 122, options [nop,nop,TS val 561024198 ecr 2401372061
+], length 0
11:26:39.565747 IP A.B.C.D.pcsync-https > clientserver.55766: Flags [P
+.], seq 1:833, ack 248, win 122, options [nop,nop,TS val 561024199 ec
+r 2401372061], length 832
11:26:39.565752 IP clientserver.55766 > A.B.C.D.pcsync-https: Flags [.
+], ack 833, win 242, options [nop,nop,TS val 2401372062 ecr 561024199
+], length 0
11:26:39.566007 IP clientserver.55766 > A.B.C.D.pcsync-https: Flags [P
+.], seq 248:255, ack 833, win 242, options [nop,nop,TS val 2401372062
+ ecr 561024199], length 7
11:26:39.566158 IP A.B.C.D.pcsync-https > clientserver.55766: Flags [F
+.], seq 833, ack 255, win 122, options [nop,nop,TS val 561024200 ecr 
+2401372062], length 0
11:26:39.566163 IP clientserver.55766 > A.B.C.D.pcsync-https: Flags [F
+.], seq 255, ack 833, win 242, options [nop,nop,TS val 2401372063 ecr
+ 561024199], length 0
11:26:39.566173 IP clientserver.55766 > A.B.C.D.pcsync-https: Flags [.
+], ack 834, win 242, options [nop,nop,TS val 2401372063 ecr 561024200
+], length 0
11:26:39.566262 IP A.B.C.D.pcsync-https > clientserver.55766: Flags [.
+], ack 256, win 122, options [nop,nop,TS val 561024200 ecr 2401372063
+], length 0

    [download]

    Also, i'm using the exact same URL as the one i'm using in SOAPUI to call the web service.
    If the parsing issue is on the response, is there any function i should use to parse/decode the response ?.

[reply]
[d/l]

      Maybe SOAP::Trace helps you. At least you get to see the headers that get sent out. If all else fails, you can then try to send the same headers and body with LWP::UserAgent directly to better see what happens without involving SOAP::Lite.

[reply]
        Hi Corion, excellent. Will try SOAP::Trace but think i will get away from SOAP::Lite ultimately. Thanks a lot.
[reply]

In Section Seekers of Perl Wisdom