Dillo browser's https not working when non-absolute path for confgfile used

Suppose you have a configfile in the current working directory. The following command will fail to load the https url in the dillo web browser (you must also make sure that there are no implicitly searched for configfiles also).

proxychains4 -f proxychains.conf dillo https://api.ipify.org

The reason is that dillo does a chdir to /tmp and then forks a "server" process. This forking causes the dll to initialize for the new process, which will eventually call get_config_path. However, since the cwd is now /tmp, get_config_path will not find a configfile and exit the process. Dillo will not be able to communicate with the (dead) server, so it won't be able to load the https url.

I believe a good fix would be to have get_config_path set the configfile envvar to the realpath of the used configfile.

Start by locating get_config_path and trace how proxychains4 -f proxychains.conf resolves the configuration before and after a chdir to /tmp. Reproduce with Dillo and https://api.ipify.org; done means the relative configuration path remains usable after the fork and the HTTPS URL loads successfully.