I have an ASP.Net web project that I am testing and debugging in VisualStudio with URL https://localhost:44300. For tests on my smartphone I start "C:\Program Files\nodejs\npx.cmd" iisexpress-proxy https://localhost:44300 to https://*:81. So I can call this website within my local network with https://[My Notebook IP]:81 .
Further, I created a dynamic DNS [mysubdomain].dynv6 and added a port forwarding from [mysubdomain].dynv6:81 to [My Notebook IP]:81 . So I can test my web app with [mysubdomain].dynv6:81 .
Of course I get warnings on a untrusted certificate. This was ok until now because I could ignore these warnings in my browser. For other reasons, however, I now need to install a proper certificate, e.g. with LetsEncrypt. The problem is that through iisexpress-proxy the incoming URL is localhost:44300, not [mysubdomain].dynv6:81. So, when I create my certificate for [mysubdomain].dynv6, this certificate will not be used.
What can I do?
I have an ASP.Net web project that I am testing and debugging in VisualStudio with URL https://localhost:44300. For tests on my smartphone I start "C:\Program Files\nodejs\npx.cmd" iisexpress-proxy https://localhost:44300 to https://*:81. So I can call this website within my local network with https://[My Notebook IP]:81 .
Further, I created a dynamic DNS [mysubdomain].dynv6 and added a port forwarding from [mysubdomain].dynv6:81 to [My Notebook IP]:81 . So I can test my web app with [mysubdomain].dynv6:81 .
Of course I get warnings on a untrusted certificate. This was ok until now because I could ignore these warnings in my browser. For other reasons, however, I now need to install a proper certificate, e.g. with LetsEncrypt. The problem is that through iisexpress-proxy the incoming URL is localhost:44300, not [mysubdomain].dynv6:81. So, when I create my certificate for [mysubdomain].dynv6, this certificate will not be used.
What can I do?
Share Improve this question edited Mar 17 at 15:48 I.sh. 2,1712 gold badges12 silver badges44 bronze badges asked Mar 17 at 15:45 Bernd MeneyerBernd Meneyer 10910 bronze badges1 Answer
Reset to default 0You may send a redirect to the client (302) .
First creating a redirect website, then on redirect web site creating an http redirection. The redirection second and third parameters are dependent on the application.