DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Related

  • GDPR Compliance With .NET: Securing Data the Right Way
  • How to Enhance the Performance of .NET Core Applications for Large Responses
  • Developing Minimal APIs Quickly With Open Source ASP.NET Core
  • Revolutionizing Content Management

Trending

  • Mocking Kafka for Local Spring Development
  • Agentic Testing: Moving Quality From Checkpoint to Control Layer
  • Architecting Zero-Trust AI Agents: How to Handle Data Safely
  • MuleSoft MCP and A2A in Production: What 17 Recipes Reveal
  1. DZone
  2. Coding
  3. Frameworks
  4. HTTPS Redirection Not Working after Migrating to ASP.NET Core 2.1

HTTPS Redirection Not Working after Migrating to ASP.NET Core 2.1

If you've come across this issue during your own migration, then this post is for you. Read on to learn the quick solve!

By 
$$anonymous$$ user avatar
$$anonymous$$
·
Aug. 28, 18 · Presentation
Likes (2)
Comment
Save
Tweet
Share
34.4K Views

Join the DZone community and get the full member experience.

Join For Free

Enforcing HTTPS is easy with ASP.NET Core 2.1, however, if after migrating a project to 2.1 you find that it still does not work, then this article will explain what to do.

The New and Shiny

ASP.NET Core 2.1 comes with new features making it easy to enforce HTTPS. New projects are enabled by default, using UseHttpsRedirection middleware in Startup.Configure to handle the redirection.

public void Configure(IApplicationBuilder app, IHostingEnvironment env)
{
    if (env.IsDevelopment())
    {
        app.UseDeveloperExceptionPage();
    }
    else
    {
        app.UseExceptionHandler("/Error");
        app.UseHsts();
    }

    app.UseHttpsRedirection();

    app.UseMvc();
}
Migratin

Migrating From 2.0 to 2.1

After migrating to 2.1 and following the Migrate from ASP.NET Core 2.0 article, I expected the HTTPS redirection to work. It didn't, but I did have this warning in the Output window.

Microsoft.AspNetCore.HttpsPolicy.HttpsRedirectionMiddleware:Warning: Failed to determine the https port for redirect.

Adding UseHttpsRedirection alone is not enough. The project must be "enabled" for SSL too. As I said earlier, new projects are enabled by default, however if you have upgraded an older project you must go into the project properties ( Alt + Enter) -> Debug and check Enable SSL.

By checking Enable SSL a value is assigned to sslPort in launchSettings.json, located in your project under Properties in the Visual Studio Solution Explorer.

As you can see below, with SSL enabled the sslPort is set to a value of 44398, whereas before it was 0.

{
  "iisSettings": {
    "windowsAuthentication": false,
    "anonymousAuthentication": true,
    "iisExpress": {
      "applicationUrl": "http://localhost:59698/",
      "sslPort": 44398
    }
  }
}

Running the application again redirects to HTTPS as expected.

Summary

For me, migrating a project to ASP.NET Core 2.1 has been simple and painless except for this one gotcha with HTTPS redirection. If you are having any problems I would definitely recommend creating a new blank project and comparing settings and files against the project you are migrating. This is how I discovered a difference in the sslPort value which led me to find the Enable SSL checkbox.

HTTPS ASP.NET ASP.NET Core

Published at DZone with permission of $$anonymous$$. See the original article here.

Opinions expressed by DZone contributors are their own.

Related

  • GDPR Compliance With .NET: Securing Data the Right Way
  • How to Enhance the Performance of .NET Core Applications for Large Responses
  • Developing Minimal APIs Quickly With Open Source ASP.NET Core
  • Revolutionizing Content Management

Partner Resources

×

Comments

The likes didn't load as expected. Please refresh the page and try again.

  • RSS
  • X
  • Facebook

ABOUT US

  • About DZone
  • Support and feedback
  • Community research

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 215
  • Nashville, TN 37211
  • [email protected]

Let's be friends:

  • RSS
  • X
  • Facebook