Map link does not work when map is located at a path relative to root

[democat3457]

Hey there, I'm trying to use this mod with a dynmap located at a URL that's at {url}/main, but the mod keeps removing the /main when trying to connect. I've narrowed it down to this line that just grabs the host domain.

The map URL I'm using is https://dynmap.minecartrapidtransit.net/main, but the mod keeps trying to connect without the /main, resulting in it unable to grab player locations.

[thebuildcraft]

Important: Did you use LiveAtlas or Dynmap as the type? (its a LiveAtlas btw)

I have tested it with this exact server countless times. Idk why it should fail now.
Also, yes it first removes the /main, but if you open that in the browser you will see that there is a config in the html code that links to the other endpoints with the full url.

[thebuildcraft]

Please let me know if it works with "LiveAtlas" so I can correct the issue title and close it.

[democat3457]

It happened with both LiveAtlas and Dynmap as the configured type @thebuildcraft. I'm not sure exactly how the LiveAtlas on the link I sent is configured or if it's even configured correctly, since I notice that the various endpoints on the root url give almost exactly the same data as the /main url.

[Xy-ks]

When deploying multiple Dynmap world maps under the same domain name and port (for example, distinguishing them via the /world1 and /world2 paths), the current URL parsing logic fails to correctly extract the complete path, which results in the inability to assemble a valid player query interface.

Relevant Code Line
Modifying the regular expression from its current pattern to:

https?://[^/?#]+(/[^?#]*)?

can resolve the issue I am encountering. However, I cannot guarantee that the paths pasted by all users require the retention of subpaths.

Apologies for any awkward phrasing – this was translated with a tool.

[thebuildcraft]

Thank you :)
I should have time to test and release an update in around 2 weeks.