Chris Ross

https://docs.microsoft.com/en-us/aspnet/core/fundamentals/servers/kestrel/endpoints?view=aspnetcore-5.0#replace-the-default-certificate-from-configuration ``` { "Kestrel": { "Endpoints": { "HttpsInlineCertFile": { "Url": "https://localhost:5001", "Certificate": { "Path": "", "Password": "" } }, ``` Note as of 5.0 it also automatically rebinds if you...

For that second requirement you'd use appsettings.production.json vs appsettings.development.json. The host should load the correct config at runtime.

Temp data? Gross. https://docs.microsoft.com/en-us/aspnet/core/fundamentals/app-state?view=aspnetcore-2.2

I did some work on this over in my fork https://github.com/Tratcher/OpenHub/commits/master. Conceptually it works pretty well using one tab per column. I still need to fill in a lot of...

Try setting the environment variable `ASPNETCORE_FORWARDEDHEADERS_ENABLED=true` on your service. This is something we do by default in the Asp.Net Core container image, but it might not be happening in the...

That variable would need to get set at the start of Program.Main before creating the host. Try the troubleshooting steps at the bottom: https://docs.microsoft.com/en-us/aspnet/core/host-and-deploy/proxy-load-balancer?view=aspnetcore-6.0#troubleshoot

Interesting, it sounds like the middleware is running and getting you those x-original-* headers. Disable the middleware and confirm you get `x-forwarded-proto: http`. This might be an ARC infrastructure issue.

This ``` app.UseForwardedHeaders(new ForwardedHeadersOptions() { ForwardedHeaders = ForwardedHeaders.XForwardedFor | ForwardedHeaders.XForwardedProto }); ``` Is conflicting with this ``` services.Configure(options => { options.ForwardedHeaders = ForwardedHeaders.XForwardedFor | ForwardedHeaders.XForwardedProto; // Only loopback proxies are...

> 2\. Our Public URL is different from Internal and redirectUri is autogenerated based on internal URL though the request starts from External Is this the expected and actual values?...

`Host: product.example.org` is your problem. Which proxy are you using? It doesn't look like it's setting the x-forwarded-Host header with the original public value. Your backend app has no way...