I went looking for up to date, self-hosted HTTP support for .NET code and it took me (after a few digressions into older solutions) to Owin which I had, curiously enough, run into by name elsewhere recently. It looks like a decent solution with katana as the project name for the open source Microsoft implementation.

The TLS support is a bit odd at first look as it doesn’t seem to directly involve the code as seen here and here . It looks as if the TLS overlay is provided outbound from the hosting application. I’ll have to look into the details later but I expect that this will be more than adequate for my purposes.

I suspect I’ll wind up creating my own local trusted root cert and installing it on my home machines. That should allow me to generate valid-ish TLS certs for local testing that look like the real thing. I’d rather have TLS on the RESTful connections as I’d much rather build this as if it were a real thing that would need to survive in the wild.

More stuff to play with as I move this forward. I’m expecting to build the machinery in one or more assemblies and then bolt them into appropriate host frames for execution. This should allow me to test as local code but then run that same code as a service once it is tested and ready.