+28We have a distributed architecture of FME Flow 2025.1.2 using our own Tomcat deployment and we’re offloading our SSL via F5 into our private IP space. The issue we’re seeing is in the FME Flow REST API Gateway is the URL used in CURL/Request example URLs are http but should be https.
We don’t believe its a CORS issue since we’re inside our domain.
Where is FME Flow getting the CURL URL? Can we change it in a config file? Or is something else going on?
+5Hi
This looks similar to a bug affecting the equivalent page for Data Virtualization APIs, which has been fixed in newer versions of Flow.
To apply this fix manually, update the FME_SERVER_WEB_URL parameter in fmeFlowWebApplicationConfig.txt and fmeFlowConfig.txt. Make a backup of these files before making any changes, and restart your Flow instance to apply them.
Both of these files are found within <FMEFlowDir>/Server. By default, <FMEFlowDir> is C:\Program Files\FMEFlow on Windows and /opt/fmeflow on Linux.
+28
+5Hi
Thanks for the update. Please feel free to submit a support ticket if you have further questions.
Happy holidays!
Skyler
