Web Request Succeeds and Returns an Error Alert

Permanently deleted user

1. November 2018 04:58

Using the "Send Web Request" activity I'm uploading a file to FME server using the data upload service. Documentation is here http://docs.safe.com/fme/html/FME_Server_Documentation/Content/ReferenceManual/service_dataupload.htm

 

When I use the upload single file PUT method, it succeeds in writing the file and the request (network response) is a 201 success. The problem is, I get a dialog back from the workflow saying "The application is experiencing issues while performing this operation."

 

If I run the same workflow again using the same file name then I do not get the error and the response is a 200 success. I can change the contents of the file and everything but if it already exists the workflow is happy.

 

EVERYTHING is the same in the first and second response EXCEPT that the failed response has a status code of 201 (Created). My _guess_ is that, if a PUT returns a 201 (Created) the workflow throws and error.

 

Info on my request...

URL: http://myServer.company.com/fmedataupload/GeocortexWorkflows/MySite_Upload.fmw/OtherName.txt?opt_fullpath=true

Method: PUT

Blob: = $getInputFileData.result (this is an array buffer)

 

 

Am I doing something wrong here or is the workflow activity failing on 201 when it shouldn't?

0

• 

  Ryan Cooney

  1. November 2018 05:39

  Hi Matt,

   

  It looks like you are right. The Send Web Request activity fails if it doesn't receive a 200 response. We'll look into the handling of all 2xx responses to see what can be done.

   

  For now you could try setting the Channel Name property on the Send Web Request activity to arcgis. This changes the underlying mechanism used to make the request to use esri.request from the ArcGIS JavaScript API.

   

  --Ryan

  0
• 

  Permanently deleted user

  2. November 2018 00:29

  Thanks Ryan, I'm looking forward to the fix.

   

  The arcgis channel didn't fix the issue because the URL is then prefixed with "http://myServer.com/Html5Viewer/proxy.ashx?" and then I get a 403 error.

   

  ^That's ok, because I found a work around using the try/catch activity in the workflow manager. I can also forward the request through a web service too. Still...it will be good to have a straight up web request running in release near here.

  0
• 

  Ryan Cooney

  2. November 2018 04:42

  Hi Matt,

   

  We've just implemented a fix for this today. It will be part of 5.8.1 in a couple weeks.

   

  --Ryan

  0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.