question

koko-3167 avatar image
0 Votes"
koko-3167 asked koko-3167 edited

Azure AD Application Proxy-Internal Url issues

Hi all,

I'm trying to use Azure AD Application Proxy to access on-premises application.
However, application url is not valid, which Azure portal displays the following error message.

"The path of the url does not end with '/' For wildcard applications the url must be in the format: http(s)://*.domain"

For example(Internal Url):
OK:"http://aaa/bbb/"
NG:"http://aaa/bbb"

I have used NG type, but I want to use it.
Please tell me how to deal with this problem.

Thanks

azure-active-directoryazure-ad-application-proxy
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

sikumars avatar image
1 Vote"
sikumars answered

Hello @koko-3167,

Thanks for reaching out.

In such scenarios, recommend to publish the application using the highest level path so that remaining path would be translated by default. In this example, it would be http://aaa/

For example, if you publish the path https://yourapp/ and when end user calls images in https://yourapp/media, they would be rendered by default therefore you don't have to publish complete path https://yourapp/media to work. Hope this helps.

127940-image.png


Please "Accept the answer" if the information helped you. This will help us and others in the community as well.


image.png (29.4 KiB)
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

koko-3167 avatar image
0 Votes"
koko-3167 answered koko-3167 edited

Hello @sikumars-msft ,

Thank you for your reply,
and also I'm sorry for the late reply.

Actually I tried that out your advice,
unfortunately it did not solve the problem.

In this example,
if I try publish the path "http://aaa/", they wouldn't be rendered by default.
that's why I don't publish when end user calls in "http://aaa/bbb/".

I'm deploying in WebSphere, it displays the following error message:

 "Error 404: SRVE0190E: File not found."

Is this a WebSphere issues?


5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.