Container app on azure configuration

Just spent a few hours trying to get this working. I had previously had something working ok in a windows web app, but when switching to a container web app under Linux, it kept on redirecting back to the insecure http://xxxxxx.azurewebsites.net/signin-oidc rather than the secure https://xxxxx.azurewebsites.net/signin-oidc

A lot of reading and trial and error and this appears to work.

services.Configure<ForwardedHeadersOptions>(options =>
{
    options.ForwardedHeaders = ForwardedHeaders.XForwardedFor | ForwardedHeaders.XForwardedProto;
    options.RequireHeaderSymmetry = false;
    options.KnownNetworks.Clear();
    options.KnownProxies.Clear();
});

And at the top of Configure

app.UseForwardedHeaders();

Is this expected behaviour? Is it documented somewhere, if so I couldn’t find it.

[guardrex]

We cover this, but it probably isn’t cross-linked well. @nrandell, it looks like you didn’t come across our topic on this in your search for a solution … https://docs.microsoft.com/aspnet/core/host-and-deploy/proxy-load-balancer

I couldn’t find it

@nrandell, what topic(s) were you using when you were working on your implementation of the container app under Linux? The simplest solution is perhaps to link that topic directly to ours.

I’ve taken note that our own Docker topics don’t link our new proxy/load balancer topic, so I’ll take care of that right now.

[jmprieur]

Closing as the documentation was moved to ASP.NET