Login problem: https://github.com/aspnet/Mvc/issues/4072
The ELB supports a HTTP header called
X-FORWARDED-PROTO. All the HTTPS requests going through the ELB will have the value of
X-FORWARDED-PROTO equal to
https. For the HTTP requests, you can force HTTPS by adding a simple rewrite rule follows this header.
Upon receiving the request the
arguments attributes on the
aspNetCore element. Core Module also sets a few environment variables for the application process –
ASPNETCORE_TOKEN. Here is where the
UseIISIntegration magic happens. When the application starts, the code inside
UseIISIntegration method tries to read these environment variables and if they are not empty they will be used to configure the url/port the application will listen on. (If the above environment variables are not set
UseIISIntegration won’t try to configure anything so that you can use your own settings when running the application directly (i.e. without IIS)). One important detail to pay attention to is where you put the call to
UseIISIntegration when configuring your application with WebHostBuilder. You need to make sure that you don’t try to set server urls after you called
UseIISIntegration otherwise the url set by
UseIISIntegration will get overwritten and your application will be listening on a different port that Core Module expects. As a result things will not work.