Publish Application Using IIS ARR Reverse Proxy With Auto Redirect

Question

question

AriefHardiansyah-8548 asked Apr 21, '22 BruceZhang-MSFT commented Apr 26, '22

Publish Application Using IIS ARR Reverse Proxy With Auto Redirect

Hi all,

We've 1 Server application internal with internal URL eclass.galicari.com

when we type in the browser with the address eclass.galicari.com it will automatically redirect to eclass.galicari.com/Account/Login?ReturnUrl=%2F
so does with https when we type with address https://eclass.galicari.com it will automatically redirect to https://eclass.galicari.com/Account/Login?ReturnUrl=%2F

Currently we have published the application using ARR reverse proxy & configured URL Rewrite with external URL eclass.pcino.fabricam.com
Is it possible when we type on browser with URL eclass.pcino.fabricam.com it will automatically redirect to https://eclass.pcino.fabricam.com/Login?ReturnUrl=%2F ?
What kind of url rewrite should we add? or there are other configurations that we have to do?
Really appreciate for your answer

windows-server-iis

· 5

5 |1600 characters needed characters left characters exceeded

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

BruceZhang-MSFT · Apr 22 at 03:19 AM

Hi @AriefHardiansyah-8548 ,

This question is very similar to your previous question, it's not complicated, but hopefully I explained it clearly enough.

I'm not sure what the difference is between your internal and external URLs. I'm guessing that your internal URL is bound directly to the content server, and the request doesn't need to go through the ARR server. The external URL is bound to the ARR server so requests need to go through the ARR server.

Since the external URL is bound to the ARR server, the mapping from DNS identification to the external domain name should be the IP of the ARR server. Even if you change the URL rewrite rule in the content server to rewrite to the external domain name, this will just result in an infinite loop of redirects.

Since the Login page is in the second segment of the URI and is not directly behind the domain name, the Default document cannot be set in the content server. Unless you place the login page directly in the website root directory, both internal and external URLs will display the Login page by default. I don't know your project type, but putting the login page directly in the root directory in asp.net and asp.net core applications may cause routing confusion.

0 ·

AriefHardiansyah-8548 BruceZhang-MSFT · Apr 22 at 08:31 AM

Hi @BruceZhang-MSFT ,

Thanks for your explanation, but when we type with eclass.pcino.fabricam.com (http without https) it will automatically redirect to eclass.pcino.fabricam.com/Login?ReturnUrl=%2F and when we type with https://eclass.pcino.fabricam.com it will automatically redirect to eclass.pcino.fabricam.com/Login?ReturnUrl=%2F

is there an incorrect URL rewrite configuration? or is there some other configuration we have to do?

Kindly need your help and advice?

0 ·

BruceZhang-MSFT AriefHardiansyah-8548 · Apr 25 at 02:03 AM

Hi @AriefHardiansyah-8548 ,

I cannot understand what you mean. But all requests to eclass.pcino.fabricam.com have been redirected to eclass.pcino.fabricam.com/Login?ReturnUrl=%2F, it looks like it has served your purpose with redirection.

Can I understand it this way, you want the https request to still be https after redirection? If so, please show your rewrite rule. I need to check it to know how you configure.

is there an incorrect URL rewrite configuration?

0 ·

Show more comments

question