AnsweredAssumed Answered

Problem with Insert from URL cURL options

Question asked by TeraKuu on Mar 6, 2019
Latest reply on Mar 12, 2019 by TSGal

We have a problem with Insert from URL script step. This affects only two of our customers and we cannot reproduce the issue on our own workstations. One of the cases is that the step works for one Windows user account and not on another non-administrator account on the same workstation.

 

Scipt step has following cURL options:

"--header \"Content-type: text/XML\""  & ¶ &

"--header \"charset=utf-8\"" & ¶ &

"-D $palauteHeaders"& ¶ &

"-d @$xml"

 

We get the expected XML data with our requested but $palauteHeaders variable is not populated in these problematic cases. When it works as it's supposed to the $palauteHeaders looks like this:

HTTP/1.1 200 OK

Server: nginx

Date: Wed, 06 Mar 2019 13:57:19 GMT

Content-Type: text/xml; charset=utf-8

Content-Length: 1160

Connection: keep-alive

Cache-Control: private, max-age=0

X-AspNet-Version: 4.0.30319

X-Powered-By: ASP.NET

 

We have recordings of this working and not working but we cannot send them to public forum. We can send them with a direct message.

 

 

Product and version: FileMaker Pro 17.0.4.400 x64

OS and version: Windows 10 Pro

Browser and version (for WebDirect only) --

Hardware: Winows PC

Description: Explained above

How to replicate: ?

Workaround (if any): None

Outcomes