Skip to main content
Question

Getting Requestor URL


hkingsbury
Celebrity
Forum|alt.badge.img+55

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?

 

 

2 replies

david_r
Celebrity
  • June 9, 2021

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.


hkingsbury
Celebrity
Forum|alt.badge.img+55
  • Author
  • Celebrity
  • June 9, 2021
david_r wrote:

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


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings