user21699

cURL Options Not setting Content Type Header

Discussion created by user21699 on Feb 20, 2019
Latest reply on Feb 21, 2019 by user21699

I'm implementing a Web Service script using Insert from URL - cURL Options.

 

I can connect with no issues and successfully add a soap file for submission but I'm getting rejected by the receiver server due to a Content-Type conflict.

 

It appears that FM16 does not send the correct values for a Header as a cURL option. If I set no Header value, then the  Content-Type is preset to application/x-www-form-urlencoded.

 

If I set the Header value to Content-Type: text/xml, the server sees it as

 

0000: HTTP/1.1 415 Cannot process the message because the content type

0040:  'application/octet-stream' was not the expected type 'text/xml;

0080:  charset=utf-8'.

 

Has anyone found a work around for this issue. It seems that FM is not recognizing any Content-Type changes. I'd like to keep this as a native function rather than using a plugin.

 

Thanks,

 

Blaine

Outcomes