Public URL Configuration
The Public URL is what you expect users of this LiquidFiles system to use when interacting with this LiquidFiles system. In the most basic example, your domain is mycompany.com and you want to use LiquidFiles using: https://liquidfiles.mycompany.com.
The Public URL configuration in LiquidFiles is available in Admin → System → Hostname & Public URL and looks like:
From the top, the System Hostname is the Internal hostname of the system, which is used for things like naming backups and similar, it's not exposed externally. You can set this to the same as the Public Hostname if you want.
The Public URL is the externally facing Protocol and Public Hostname and is used for most thing in LiquidFiles like when sending email links and similar.
The Force Protocol Settings determines what happens when someone connects to the system using the non-preferred method, i.e. what should happen if someone connects using HTTP and you have selected the Public URL to be HTTPs. There's three settings:
|Force HTTPs||In this mode, all traffic is forced to use https. Connections on http will be instantly redirected to https. This is the default.|
|Force HTTP||All traffic is forced to use http. Connections on https will be instantly redirected to http.|
|Permit either HTTP or HTTPs||With this setting, LiquidFiles does not care if users use HTTP or HTTPs, this is the preferred setting when using a Reverse Proxy with LiquidFiles.|
Force Hostname in URLs
The Force Hostname in URLs determine what happens with redirects when someone connects using a different Public Hostname (such as the systems IP address) than what's specified in the Public URL.
If the Public URL is https://liquidfiles.company.com and you connect with https://10.20.30.40 (assuming this is the IP address of the LiquidFiles system), with the setting to Force Hostname in URLs, when you're logging in from https://10.20.30.40, you will be redirected to https://liquidfiles.company.com/... With this setting to Not Force the Hostname in URLs, you will be redirected to https://10.20.30.40/...
Setting the Force Hostname configuration can make troubleshooting more difficult.
Where the Force Hostname in URLs can improve security is what happens when someone connects and does not enter an IP address as the connecting IP address (as they should according to the specification), but since the HTTP specification dictates that any redirect needs to include a hostname or IP address, if the setting is set to Not Force Hostname in URLs, LiquidFiles will insert it's own IP address in the URL and security audits will pick this up that LiquidFiles is "leaking" it's internal IP address. If you belive this to be a security problem you can set LiquidFiles to Force the Hostname in URLs. Please see: Web Server Redirect Configuration documentation for more Information.