The automatic resource loading URL detection that is currently used fails in several more complex scenarios and also in some standard scenarios depending on reverse proxy configuration.
To better help customers in such cases, we should make the resource loading URL (optionally) configurable.
Possible options will be:
Automatic detection (default value):
The exporter tries to guess the resource loading base URL at the beginning of an export and uses the found URL. This is the current approach.
A base URL configured by an administrator is used. You can directly point to a tomcat connector here.
No HTTP based resource loading:
Only the in-process resource loaders are used. When this option is selected no image effects are supported. The integration with Scroll Versions will not consider this setting as it can not work without it.