HTTP Task Experience
Summary: Stefan is seeking advice on utilizing the HTTP Task in Workflow Designer, as his current experiment with it results in a timeout after 10 seconds. Another member, Sean, questioned the type of authentication used and suggested checking the Edge connection and setting up an error boundary event to identify HTTP codes. Stefan responded that the issue was related to a man-in-the-middle proxy, explaining that the task doesn't use the proxy, posing problems with external network access. While internal endpoints work for their use case, accessing external ones would require additional solutions.
Hello Data Citizens,
does anyone of you have experience with the HTTP Task in Workflow Designer?
We are currently experimenting with it but are not able to make it work. It always times out after the hard coded 10 seconds.
If anyone had similar problems and were able to solve them I would be glad if you could share your experience here.
Cheers,
Stefan
Sean Pyle
·1 year agoCurious if you got this to work Stefan. What type of authentication were you trying to run (OAuth, Pass or Basic)? I found that OAuth only works with grant-type client credentials, so that was my issue when I tried using it initially. Also wondering if you ran the test inside your Edge connection to verify the credentials were accurate.
If you think it's with the process and not the Edge connection, I recommend setting up an error boundary event to look for different HTTP codes like "HTTP400". That might help you narrow it down.
stefan_busch
OP1 year agoHi Sean,
I kinda got it working.
The thing is we have a man-in-the-middle proxy, which is no problem for the normal operation of the edge site (like ingestion of metadata from our on-prem data sources) but it looks like that if you use the http task then edge does not use the proxy. So accessing http endpoints that are inside our own network are not a problem, but we can not access endpoints that are outside of it.
Luckily our use case right now it to access internal endpoints so this works out for us but if we wanted to connect to external endpoints it would not work OOTB (we could in theory write a little dummy endpoint on one of our internal servers that forwards requests to external endpoints and then send the answer back to the edge server).