Does this work when using On premise gateway?

[am071092]

Hi, I am getting an UnresolvableHostName when invoking an http request. Its not able to resolve the location url.

[jeffhollan]

It should work with on-premises data gateway, as I'm creating the callback URL from whatever URL initially invoked it:

LogicAppsAsyncResponseSample/AsyncResponse/Controllers/AsyncController.cs

Line 33 in 1162ff9

responseMessage.Headers.Add("location", String.Format("{0}://{1}/api/status/{2}", Request.RequestUri.Scheme, Request.RequestUri.Host, id)); //Where the engine will poll to check status

However possible something here amiss. Just confirming you get an error from the logic app run and not the app itself? Curious to know what the URL generated in line above looks like when called on premises through gateway

[nacharya-msft]

I am trying to use this through on-premise gateway and get UnresolvableHostName when invoking http request that was in the location Url as well. My location Url is {location: https://nacharya-hb16/api/values?dc=BN3P&correlationId=ADLS&guid=46a334c8-9a42-455e-aa0c-09d0719e9941} as expected,

nacharya-hb16 is the machine name where gateway is installed. Also I use this Url from a browser, and it works as expected (so no connectivity issues). Additionally, https://nacharya-hb16/api/values?dc=BN3P&correlationId=ADLS is a URL that can be reached from flow through gateway to my web api (original URL), but the URL that is returned with a guid (due to long running operation) fails to connect (UnresolvableHostName) through flow.

[nacharya-msft]

I am able to confirm that on upcoming release, I am able to use async pattern as described here using On premise data gateway. The release should be publicly available end of August 2018.

Thank you Flow team for active engagement and fixing a bug.