HTTP Web Request - "Illegal characters in path" error

posted on September 14, 2022 • Show version history

Hi all.

We have a GET web request in a workflow that uses a URI formed with a Transaction ID (guid) and File ID (guid) - and no matter whether we use tokens or hard-code the values in the URI we get the error 'Illegal characters in path'.

The exact same URI can be used (copy-pasted, hard coded obviously) in Postman to get the files in question - no issues.

This web service is used several times in the same workflow (previous tasks) to create, check and retrieve the transaction/file IDs themselves in the other application - so we know we have no issues with the Web Service settings, Authorization Headers, or anything else related to the query.

Workflow seems to be having some issue constructing the full request path.

We've tried changing the Web Service stem to use different elements (i.e. remove the '/api/' or other stems from the URI and put them in the Web Service) but nothing seems to work.

Just checking to see if anyone has seen this issue previously, and if so, what might have been the cause or something we could look into/try. We're really scratching our heads, as it looks absolutely correct from all angles; and as mentioned, works fine in Postman.

Thanks for any ideas!

UPDATE NOV 2022: This has been resolved in the latest version of Workflow. If you have this issue please update LF Workflow and republish. You should see the issue is fixed.

0 0

replied on September 14, 2022

For testing, I would create a new token and put your URI into it and then track the token to see if it is containing what you think it is. You may need to open the token editor on each token and add URL encoding.

2 0

View 1 previous reply

replied on September 14, 2022 • Show version history

Thanks Bert - really appreciate your suggestion. We had tried using a token create/modify step prior to the request before, and no joy - but hadn't thought to encode as a URI, so we were really hopeful that would be the issue, but alas - still not working.

The URI generated by that token can (as usual) be copy/pasted into Postman and the request is successful.

I should also say that the 'encoded as URI' version looks identical to what we use when we hard-code the GUID values in.

Very weird!

0 0

replied on November 12, 2022

Hi Duncan!

Were you able to find a solution for this?

I am also facing the same issue. I'm trying to retrieve a file using its ID but the Web request shows as "Illegal characters in path". But the request works fine in Postman.

I would really appreciate some guidance on how to solve this.

1 0

replied on November 12, 2022

Hi Steffany,

This was noted by Laserfiche as an issue, and has been resolved in the latest version of Workflow.

Installing the most recent Workflow update then republishing it got it working for us.

Good luck!

0 0

replied on November 12, 2022

Thank you so much for your prompt reply.

I am currently using workflow designer 10.4.3, let me see if I can get the latest version of workflow to fix this issue.

Thank you once again!

0 0

Discussion

Discussion

HTTP Web Request - "Illegal characters in path" error

Comments 5

Follow-Ups 0

Sign in to reply to this post.