Solved

HTTPCaller SOAP 404


Badge +1

Before describing my issue, I already looked into the list of posts underneath:

Because I first didn't succeed, I also installed SoapUI, as advised by @daveatsafe. And within SoapUI everything works fine. When I go to FME and use the HTTPCaller, I get an "HTTP/1.1 404 Not found"

In the header I already added the SOAPAction (both with and within double quotes) and also copied all the other header elements and values in the header request. But still no difference.

I also tried WireShark to look into the POST-requests, but since they're all encoded, I do not seem to be able to find any differences (and I can't succeed in decoding them, which seems to be possible). What I did notice in SoapUI is a different URL the POST-request seems to be send to, but when questioning that at my client, they tell me to use the 'common' WSDL URL from their service.

The client made an exception on their firewall for my IP-address, so there is no use in sharing the URL.

 

I hope anyone has suggestions, e.g. how to look into the raw message FME sends or any other tip!

icon

Best answer by nielsgerrits 15 June 2020, 16:29

View original

2 replies

Userlevel 6
Badge +31

"On Windows, calls to localhost (127.0.0.1) cannot be captured because they do not trigger TCP/IP activity on that operating system so you will probably need to host the web service on a machine different from the SOAP client or try alternative solutions suggested on the Wireshark Wiki."

 

See https://glenmazza.net/blog/entry/soap-calls-over-wireshark

 

Also see https://glenmazza.net/blog/entry/switch-soap11-to-soap12 for wireshark results.

Had to look up my notes but what took me a while is to find out I needed different content types for SOAP 1.1 vs SOAP 1.2. Not sure if this is your problem, just sharing.

SOAP

Content-Type

1.1

text/xml

1.2

application/soap+xml

 

Also the namespaces are different:

Schema for the SOAP/1.1 envelope

http://schemas.xmlsoap.org/soap/envelope/

Schema defined in the SOAP Version 1.2

https://www.w3.org/2003/05/soap-envelope/

 

If this does not solve you issue I also can send a part of my functioning workspace by mail.

Badge +1

"On Windows, calls to localhost (127.0.0.1) cannot be captured because they do not trigger TCP/IP activity on that operating system so you will probably need to host the web service on a machine different from the SOAP client or try alternative solutions suggested on the Wireshark Wiki."

 

See https://glenmazza.net/blog/entry/soap-calls-over-wireshark

 

Also see https://glenmazza.net/blog/entry/switch-soap11-to-soap12 for wireshark results.

Had to look up my notes but what took me a while is to find out I needed different content types for SOAP 1.1 vs SOAP 1.2. Not sure if this is your problem, just sharing.

SOAP

Content-Type

1.1

text/xml

1.2

application/soap+xml

 

Also the namespaces are different:

Schema for the SOAP/1.1 envelope

http://schemas.xmlsoap.org/soap/envelope/

Schema defined in the SOAP Version 1.2

https://www.w3.org/2003/05/soap-envelope/

 

If this does not solve you issue I also can send a part of my functioning workspace by mail.

Allthough it was not the solution (I was provided a wrong URL), changing the Content-Type did the job after getting the right URL.

Thanks Niels!

Reply