Geeks With Blogs

News Please visit me at my new blog!!

profile for Aligned at Stack Overflow, Q&A for professional and enthusiast programmers
"free in Christ Jesus from the law of sin and death." Romans 8:2 (ESV) Check out the Falling Plates video on YouTube.
more about the Gospel
And then listen to Francis Chan speaking at LifeLight in SD.

Programming and Learning from SD

I've learned a lot about Asp.Net Core RC2, Kestrel and ports as I failed in various attempts to get a http to https redirect. I share this as a retrospective for myself and in hopes of helping you avoid the swamp and to stay on the narrow road.


Host Asp.Net with Kestrel without IIS for an internal app. I'd like to hit the machine at http://machine-name/ and get redirected to a login at https://machine-name without ports.

If they hit http(s)://machine-name/index.html without an authentication cookie, it must redirect them to https://machine-name to login.

Note: The official recommendation is to use IIS or nginx, but I want to avoid installing it on these machines and this will be internal network access. In the past I've relied on IIS and "defaults on http and https being 80 and 443 and hidden port magic" as Ben Adams on the #kestrel channel put it. Therein pointing out another abstraction Microsoft has helped me out with for many years and something I need to learn more about.

See more of my journey and some code.

Posted on Wednesday, June 1, 2016 4:25 PM ASP.Net , Build Tools , DevOps , Asp.Net Core | Back to top

Comments on this post: Https Redirect with Asp.Net Core RC2 And Kestrel on Windows

No comments posted yet.
Your comment:
 (will show your gravatar)

Copyright © Aligned | Powered by: