IIS + UseForwardedHeaders + System.Web.HttpContext.Current.Request.Url

[nunomiguelsilvagoncalves]

I created a brand new MVC .Net Framework App.

Then i used the Microsoft Project Migration Extension to create a new .Net Core App.

Changed the .Net Framework App to add

protected void Application_Start()
{
...
this.Application.AddSystemWebAdapters()
.AddProxySupport(options =>
{
options.UseForwardedHeaders = true;
});
}

I run the app in IISExpress and when i check the System.Web.HttpContext.Current.Request.Url value in the .Net Framework i have the .Net core url.

Then i change the hosting of the apps to run in IIS. I create 2 Application with 2 different Pools

Now when i check the System.Web.HttpContext.Current.Request.Url i have the .Net Framework url.

Am i missing something?

Thx

[twsouthwick]

@nunomiguelsilvagoncalves I was able to reproduce it this way:

1. Set up SiteCore to be on port 80
2. Set up SiteFramework to be on port 5005 (not important)
3. Deploy sites to both of these and set up configuration
4. Accessing framework site via proxy shows it's on 5005.

Is this the set up you're seeing? This is a definitely a bug, but want to verify that it is the right issue you're seeing.

So, specific questions: what are the urls of the core and framework apps for you? What are you seeing when proxied?

[nunomiguelsilvagoncalves]

Yes. It was something similar. In my situation I had 2 applications inside port 80. I realized that was the problem and created 2 sites in 2 different ports and now I am able to proceed with the migration. thanks From: Taylor Southwick ***@***.***> Sent: 7 de julho de 2022 23:16 To: dotnet/systemweb-adapters ***@***.***> Cc: Nuno Gonçalves ***@***.***>; Mention ***@***.***> Subject: Re: [dotnet/systemweb-adapters] IIS + UseForwardedHeaders + System.Web.HttpContext.Current.Request.Url (Issue #80) @nunomiguelsilvagoncalves<https://smex-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2fgithub.com%2fnunomiguelsilvagoncalves&umid=57950890-a8fe-4c7c-bed9-a37aa66e6204&auth=c5c198c3615b5404e4a9b115216a8376d1698b60-bc80e8bec03205ca94bd44c0e64eedb6e341ab78> I was able to reproduce it this way: 1. Set up SiteCore to be on port 80 2. Set up SiteFramework to be on port 5005 (not important) 3. Deploy sites to both of these and set up configuration 4. Accessing framework site via proxy shows it's on 5005. Is this the set up you're seeing? This is a definitely a bug, but want to verify that it is the right issue you're seeing. - Reply to this email directly, view it on GitHub<https://smex-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2fgithub.com%2fdotnet%2fsystemweb%2dadapters%2fissues%2f80%23issuecomment%2d1178289657&umid=57950890-a8fe-4c7c-bed9-a37aa66e6204&auth=c5c198c3615b5404e4a9b115216a8376d1698b60-2c6eb91a95ff1e625a964325050c11de91fb83f7>, or unsubscribe<https://smex-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2fgithub.com%2fnotifications%2funsubscribe%2dauth%2fAFOQRCXO3AVPD2NA3XUPPHTVS5JK3ANCNFSM52E4B7VA&umid=57950890-a8fe-4c7c-bed9-a37aa66e6204&auth=c5c198c3615b5404e4a9b115216a8376d1698b60-305a7385fdab66b3d82df340d2b6026daf804583>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>

[twsouthwick]

Great! Once this is merged in, should be fixed, then!