Win-acme: Add support for ASP.NET Core 1.0

[UweKeim]

Having an ASP.NET Core 1.0 website (formerly known as ASP.NET 5) hosted in an IIS 8, I do see that the challenge-url cannot be reached

The ACME server was probably unable to reach http://tm.uwe.co/.well-known/acme-challenge/...

Check in a browser to see if the answer file is being served correctly.

...

I'm both a Let's Encrypt beginner and an ASP.NET Core 1.0 beginner.

My impression is that ASP.NET Core 1.0 brings its very own web server that is called by IIS and therefore the automatic providing of those ACME challenge URLs fail.

My suggestion:

Please add support for ASP.NET Core 1.0.

[rkerber]

I would say this is probably a web.config issue.

Take a look at the wiki. The MVC changes might fix it for you.

[UweKeim]

I don't think so.

One of the current entries of my web.config is:

<add 
    name="httpplatformhandler" 
    path="*" 
    verb="*" 
    modules="httpPlatformHandler" 
    resourceType="Unspecified" />

I tried to add the content from your link but this renders my website defect, showing only the HTML as source code.

Maybe I could add your web.config changes, run the letsencrypt tool and remove it again.

Even if this would work, my understanding is that I would have to do it every half of a year for every reneval. This seems impractical to me.

[rkerber]

You should be changing the web_config.xml file in the root of the letsencrypt-win-simple application's folder. Not the web.config at the root of your site.

The web_config.xml is copied to /.well-known/acme-challenge/web.config every time you run the app. That shouldn't interfere with the rest of your site.

If you still can't get it to work, lookup how to serve extensionless files with ASP.NET Core 1.0, as it is a web.config change so ASP .NET Core 1.0 can serve up the extensionless files.

If you get it working with a different web.config than is currently on the Wiki, please add it to the Wiki so anyone else with your issue can see how to get it to work.

[UweKeim]

Thanks and sorry, I suck at reading :confused:

After changing the web_config.xml as described in the MVC section of the wiki, everything worked as expected.

[twodawg]

I had the same problem. In my case, I also had to add this code into my Startup.cs.

Also, be sure to add the .well-known directory. It is a hidden folder - so use the name, ".well-known." (the trailing dot will disappear). Windows will not allow a new hidden folder without the beginning and trailing dot.

```using Microsoft.Extensions.FileProviders;
using System.IO;
using Microsoft.AspNetCore.Http;
public class Startup
{
public void Configure(IApplicationBuilder app, IHostingEnvironment env)
{
app.UseStaticFiles();
app.UseStaticFiles(new StaticFileOptions
{
FileProvider = new PhysicalFileProvider(Path.Combine(Directory.GetCurrentDirectory(), @".well-known")),
RequestPath = new PathString("/.well-known"),
ServeUnknownFileTypes = true // serve extensionless files
});
}
}