You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to propose an enhancement to add support for a configurable base path (or base URL) for the WebAdmin interface. This feature would make it easier to deploy the interface behind a reverse proxy, such as Nginx, when serving it on a subfolder (subpath) rather than the root URL.
For example:
If the WebAdmin interface is served at https://domain.tld/stalwartadmin/, the application should be able to handle the /stalwartadmin/ prefix in URLs seamlessly.
The nginx configuration would probably look like this:
Many modern web interfaces allow working behind reverse proxies on a sub-path, for example gitea allows setting the ROOT_URL, and the rspamd web interface even works on a sub-path without any configuration.
The text was updated successfully, but these errors were encountered:
Hi,
I would like to propose an enhancement to add support for a configurable base path (or base URL) for the WebAdmin interface. This feature would make it easier to deploy the interface behind a reverse proxy, such as Nginx, when serving it on a subfolder (subpath) rather than the root URL.
For example:
If the WebAdmin interface is served at
https://domain.tld/stalwartadmin/
, the application should be able to handle the /stalwartadmin/ prefix in URLs seamlessly.The nginx configuration would probably look like this:
Many modern web interfaces allow working behind reverse proxies on a sub-path, for example
gitea
allows setting theROOT_URL
, and therspamd
web interface even works on a sub-path without any configuration.The text was updated successfully, but these errors were encountered: