#1238 IP used in paths instead of hostname or relative

[Eduo Gutierrez]

I'm running itop in a docker container for demonstration purposes for my company.

Several images produce an absolute URL that points to the IP number, and most URLs are absolute pointing to the host defined in the configuration.

Ideally all URLs should be made relative to the project root but, if this is not possible (can't imagine why, but can happen) at least all URLs should point to the hostname defined in the configuration.

When run under docker the IP that iTop "sees" has no bearing with the actual IP exposed to the outside world, so nobody accessing iTop would be able to see the images linked in this way and would see only errors. The same extends to any URL that's built with the IP.

[Romain Quetiez]

There are two kinds of URLs in an iTop page: relative to the URL used for accessing the page, and absolute based on the configuration file.

If the page is accessed by the same URL as the one given in the configuration file, there should be no issue.

Do you confirm that when you access iTop via the URL defined in the configuration file, it is working fine?