All I need is a simple redirect, is Abyss suitable?

Feek

Hi folks,
I have what I hope is a simple request and I would like to know if Abyss is suitable for me.
I run an application on a Windows 10 box that has a web interface on a custom port and address.
I own a domain where the A record is my own static IP and I'm port forwarding external port 80 to internal port 4856. The app works perfectly when addressed the following way:
http://heresmywebsite.com/hereisthepage
(obviously those aren't the correct pages etc).
I want to be able to remove the /hereisthepage.
So I need to set up a simple web server on this Windows 10 PC that will respond to http://heresmywebsite.com and redirect it to http://heresmywebsite.com/hereisthepage
Therefore I need to install a server, tell it to listen to port 4856 and redirect / to /hereisthepage
Can I do this?
Thanks.

admin

There is an even better option in Abyss Web Server. It is called reverse-proxy:
You set Abyss Web Server to shield the internal application and even have HTTPS while being served from the internal Web server.
The setup is described in https://aprelium.com/abyssws/articles/reverse-proxy.html .
But you may also need to set up some redirections in case your internal Web site has some hard coded paths and cannot live without them.
The best is to contact our support by email and we'll assist you with the best setup.

Feek

Thanks for the reply.
Actually I found an even easier solution - I enabled IIS in Windows 10, added a binding to the port and a redirect. It was as straightforward as that!

admin

Feek wrote
Thanks for the reply.
Actually I found an even easier solution - I enabled IIS in Windows 10, added a binding to the port and a redirect. It was as straightforward as that!

But this won't shield your application freely with HTTPS and a automatic certificate. It also requires that you use a non standard port.
+ don't forget that IIS has a limit of the number of concurrent connections in non-server versions of Windows.
Abyss Web Server X1 can fit the bill for free if you're interested and it has less overhead that IIS + HTTPS support with a free certificate.

Feek

Thanks again.
I've been looking into https and it seems as though the application I'm running does not support it at all. It will only serve to http. If I can force it to work then that's a decent thing.
I'm running Virtual Radar Server.
By default it runs at http://mywebaddress/virtualradar
When I installed it, I told it to listen on port 747 just to get it away from port 80. I can put that back to port 80 if needed.
My A record points to my static IP. I have forwarded port 80 in my router to port 747 on the Windows 10 PC.
In IIS I've set up a binding on port 747 and a redirect to http://mywebaddress/virtualradar
Therefore, if anyone goes to http://mywebaddress, they get forwarded to http://mywebaddress/virtualradar
If Abyss Web Server X1 can make this work with https and a certificate then I'm definitely interested. Do you think that's possible?
Thank you.

admin

Feek wrote
If Abyss Web Server X1 can make this work with https and a certificate then I'm definitely interested. Do you think that's possible?
Thank you.

This looks very possible provided that you change your setup as follows:
* Install Abyss Web Server and configure your router to port forward external port 80 to your internal port 80 and external 443 to internal 443.
* Configure the only host of X1 to have a Let's Encrypt certificate and HTTPS as explained in https://aprelium.com/abyssws/articles/using-acme-cert.html .
* Check that the default host you have is working fine in both HTTP and HTTPS.
* Now in Abyss Web Server's console, press Configure at your host and select Reverse-Proxy and add a new rule with the following details:
Local virtual path: /
Remote server address: 127.0.0.1 (or the IP of the server where Virtual Radar is installed)
Remote port: 747
Remote virtual path: /
Alternatively, and if the above does not work, use /virtualradar as both local and remote virtual paths in the rule.
Validate and restart the server. Now accessing https://mywebaddress/virtualradar should work fine. Under the hood, your .NET app with its HTTP server does not know that it is being accessed by Abyss Web Server which is kind of wrapping its output in HTTPS and enforcing what a full featured Web server has to do with a browser.
Please let us know how this works for you.
Once all is finely setup, you can make it HTTPS only by following the recipe in https://aprelium.com/abyssws/articles/using-dual-hosting.html to make all HTTP requests redirected to HTTPS on your site.

Feek

Thanks - I'll give this a try over the next few days when I have some spare time.

admin

Feek wrote
Thanks - I'll give this a try over the next few days when I have some spare time.

You're welcome. Please don't forget to go back here and share your feedback with us.