Publishing DAB through Microsoft Web Application Proxy

HI,

I setup an container with DAB. Internally everything seems to be working fine, now i want to expose DAB to the internet with AzureAD as authentication method.

I published the External URL on WAP but the "next link" in the results still points to the internal link.

External link: https://integration.someurl.nl/
Internal link: http://somehostname.local:5555/
Webapplication Proxy: Microsoft Web Application Proxy (Windows Server 2019)

Result json externally:

"nextLink": "
[http://somehostname.local:5000/api/addresses?$after=W3siVmFsdWUiOiI0QzYxMzgwQi1GQjA1LUVFMTEtQjVENy0wMDE1NUQwQTcwM0IiLCJEaXJlY3Rpb24iOjAsIlRhYmxlU2NoZW1hIjoiZGJvIiwiVGFibGVOYW1lIjoiRmlsdGVyZWRBNFNBZGRyZXNzZXMiLCJDb2x1bW5OYW1lIjoiaWQifSx7IlZhbHVlIjoiNEM2MTM4MEItRkIwNS1FRTExLUI1RDctMDAxNTVEMEE3MDNCIiwiRGlyZWN0aW9uIjowLCJUYWJsZVNjaGVtYSI6ImRibyIsIlRhYmxlTmFtZSI6IkZpbHRlcmVkQTRTQWRkcmVzc2VzIiwiQ29sdW1uTmFtZSI6IkN1c3RvbWVyIn1d"](http://integration.quality-textiles.cloud:5000/api/addresses?$after=W3siVmFsdWUiOiI0QzYxMzgwQi1GQjA1LUVFMTEtQjVENy0wMDE1NUQwQTcwM0IiLCJEaXJlY3Rpb24iOjAsIlRhYmxlU2NoZW1hIjoiZGJvIiwiVGFibGVOYW1lIjoiRmlsdGVyZWRBNFNBZGRyZXNzZXMiLCJDb2x1bW5OYW1lIjoiaWQifSx7IlZhbHVlIjoiNEM2MTM4MEItRkIwNS1FRTExLUI1RDctMDAxNTVEMEE3MDNCIiwiRGlyZWN0aW9uIjowLCJUYWJsZVNjaGVtYSI6ImRibyIsIlRhYmxlTmFtZSI6IkZpbHRlcmVkQTRTQWRkcmVzc2VzIiwiQ29sdW1uTmFtZSI6IkN1c3RvbWVyIn1d%22)

Which points to the internal addres instead of externally.

Am i missing a parameter or configuration in DAB?

Kind regards,
Rogier

Start by reviewing how DAB constructs the pagination nextLink in responses when deployed in a container behind Microsoft Web Application Proxy and Azure AD. Reproduce the reported external request and compare the generated internal and external URLs; done means nextLink resolves through the published external URL rather than the internal host.

Escrito por el modelo de indexación a partir del texto del issue.