I realize now that IIS cannot be used on Windows Server 2016 to host a gRPC Service (I'd need Windows Server 2022).
However .. the somewhat ambiguous MS docs seem to indicate that Kestrel could be used .. so I'm wondering how to properly set that up (in configs or c# code) on Windows 2016 Server?
I just read that Kestrel listens to All ports on an ip so that would be a problem as I have several IIS web sites running.
I just encountered an older link from a few years ago that described having IIS work as a reverse proxy and forward the request to a specific port that Kestrel is listening on?
That sounds rather advantageous as I could use the IIS SSL certificates that are already setup (and auto renewed) for the web site domain I intend to use.
So my question is .. how do I make this work? Has anyone used Kestrel on a production server or possibly used IIS to reverse proxy to to Kestrel
I was Not successful with get Kestrel to host a gRPC HTTP/2 service on Windows Server 2016.
It may be possible using some routine technique but I realized with I tested the localhost Kestrel version that it was taking 10x a long to return a query to Postman located on the server as it took to get the Same request using gRPC Json Transcoding (using Postman as a client) from several hundred miles away on my development box.
So what I learned is that Json Transcoding provides a quite decent response time and I'll just upgrade to HTTP/2 gRPC when I move the server to Windows 2022 or above.