Skip to main content
  • EN

Hey,

 

We have an external application at https://service.externalapp.co.nz/map/appname

 

This app, using the fmedatastreaming service calls a workbench on our FME Server at https://fme.externalapp.co.nz/fmedatastreaming/repo/workbench.fmw

 

I'm wondering whether FME Server can capture the request URL of our external application and pass that through to the workbench.

 

I've had a look at the FME_SERVER_REQUEST_HEADERS, FME_SERVER_REQUEST_PARAMETERS and FME_SERVER_REQUEST_URI parameters and none of them include it.

 

Any one have any ideas?

 

 

If you look at the job log, you can search for externalapp.co.nz and see if it's transferred to the workspace at all. If you cannot find the URL in the log file, the workspace won't be able to access it.

If you look at the job log, you can search for externalapp.co.nz and see if it's transferred to the workspace at all. If you cannot find the URL in the log file, the workspace won't be able to access it.

Hey David, yea I can see externalapp.co.nz. I'm really after the entire URL (https://service.externalapp.co.nz/map/appname). I have spoken with the PM and Dev on the project and an option we have considered is to configure an additional header be sent with the call containing the pages url and this should be picked up by FME_SERVER_REQUEST_HEADERS.

 

Unfortunately it's a lot easier and quicker for us to get backend/FME changes through the QA process than it is to get front end changes through

Reply


Community Stats

30,352
Posts
115,344
Replies
38,087
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.