Web Session Entry Template Ignores Host Custom Host Port Variable

As the title suggests, I am using Host Entries with linked (session) Entry templates from a data source's shared vault.

This is happening on Windows, Remote Desktop Manager 2025.2.30.0 (64bit). I haven't tested the issue in other versions.

Unlike a RDP or SSH session entry, where there is a bespoke port setting on the "Common > General > General" entry properties, a Web Session entry doesn't have this.

So there are two options to address this on a regular/non-templated Web Session entry, either define the website like https://mysite.example:1234, or https://mysite.example:$PORT$, where $PORT$ is pulled from "Advanced > Advanced > Advanced > Custom host port" entry properties in this scenario. Both of these methods work exactly as expected when launching an entry like this.

However, when using a Host Entry and linking a Web Session Entry Template to the Host, it appears that "Advanced > Advanced > Advanced > Custom host port" of the Host Entry properties is not respected. I have tried every combination I can think of when configuring both the Host Entry properties and the Web Session Entry Template properties and I can't seem to get it to properly apply/inherit the "Custom host port" from the Host Entry, and unless I set the "Custom host port" on the Web Session Entry Template, then $PORT$ always seems to return 80. The template is also using $NAME$ as part of the defined website URL, which is correctly pulling the $NAME$ variable of the Host Entry. So it looks like https://$NAME$:$PORT$.

When I use the Variables "browser" when editing the properties of the Host Entry, I see the correct custom port number reflected in $PORT$. This is the same for when I just have a regular Web Session Entry that is not templated or inheriting any other configurations, but yeah, the template launched from the Host Entry doesn't seem to pick this up.

In the "Common > General > General" settings of the Host Entry, I have tried setting/unsetting Use template information; the other two options here are using settings from the template.

In the "Common > Template settings > Usage" settings of the Web Session Entry Template, I have tried all three combinations of the Port usage in tandem with changing the Host Entry's Use template information setting, with no change. It always returns 80.

If I set the Host Entry to not inherit the host from the template and instead set $NAME$:$PORT$, then this kind of works for launching the Web Session Entry Template, but naturally breaks any other templates because example.host:22 naturally isn't a valid hostname.