[Feature] Automatic HTTP to HTTPS redirection

[KARMA-UA]

Is your feature request related to a problem?

Currently, when SSL is enabled, TorrServer works perfectly on the secure port (e.g., 443). However, if a user enters the domain name in a browser without explicitly typing https://, the browser defaults to an unencrypted HTTP connection (on port 80).

To ensure a secure connection, users currently have to:

1. Manually type the full https:// address every time.
2. Or set up external workarounds like Nginx reverse proxies or custom redirect scripts.

Describe the solution you'd like

It would be a great addition to have a built-in option to automatically redirect all incoming HTTP traffic to HTTPS (301 Redirect).

Ideally, when the --ssl flag is active, there could be an optional parameter (or a default behavior) that listens on port 80 and seamlessly moves the user to the secure version of the site.

Why this is useful:

• Security: Ensures that all users always use an encrypted connection by default.
• Simplicity: Keeps the "single binary" philosophy of TorrServer without requiring extra software (like Nginx or Python scripts) for a simple redirect.
• Better UX: Makes the web interface more professional and easier to access for end-users.

Thank you for the amazing work on TorrServer!

[pavelpikta]

Is your feature request related to a problem?

Currently, when SSL is enabled, TorrServer works perfectly on the secure port (e.g., 443). However, if a user enters the domain name in a browser without explicitly typing https://, the browser defaults to an unencrypted HTTP connection (on port 80).

To ensure a secure connection, users currently have to:

1. Manually type the full https:// address every time.
2. Or set up external workarounds like Nginx reverse proxies or custom redirect scripts.

Describe the solution you'd like

It would be a great addition to have a built-in option to automatically redirect all incoming HTTP traffic to HTTPS (301 Redirect).

Ideally, when the --ssl flag is active, there could be an optional parameter (or a default behavior) that listens on port 80 and seamlessly moves the user to the secure version of the site.

Why this is useful:

• Security: Ensures that all users always use an encrypted connection by default.
• Simplicity: Keeps the "single binary" philosophy of TorrServer without requiring extra software (like Nginx or Python scripts) for a simple redirect.
• Better UX: Makes the web interface more professional and easier to access for end-users.

Thank you for the amazing work on TorrServer!

Some older devices require HTTP, and automatically redirecting them to HTTPS may break their functionality.

[KARMA-UA]

I completely agree that backward compatibility is the top priority for TorrServer.

However, for those using modern clients, having an optional redirect would be a great quality-of-life improvement. What if we implement this as an "Opt-in" feature?

It could be handled in one of these ways:

• CLI Parameter:
  --force-https — A simple flag to enable the redirect on startup.

• Config/Web UI Toggle:
  "HTTPRedirect": true — A setting in the JSON config or a checkbox in the Settings menu (disabled by default).

This approach ensures that older devices won't break (since they'll keep using HTTP by default), while modern setups can be secured with a single toggle.

What do you think about such a compromise?