Persistent localStorage not working when accessing web applications through Devolutions Gateway

Hello,
we are running into an issue when accessing web applications through the Devolutions Gateway.
When connecting directly (without the Gateway), user-specific settings of the web application are stored in the browser’s localStorage and persist across sessions as expected.

However, when connecting through the Gateway, these settings are lost every time the session is closed and reopened. After some analysis, the reason seems clear:

• The browser only persists localStorage per origin (scheme + host + port).
• When using the Gateway, the session is usually exposed as https://127.0.0.1:<randomPort> or via a dynamic relay path.
• Because the port/path changes on every connection, the origin is never the same.
• As a result, the browser creates a new, empty localStorage container each time, and the previously saved settings are not visible anymore.

This is not an issue with cookies (those might be handled differently), but specifically with localStorage, since it is strictly tied to the origin.

Question:
Is there any way to configure the Gateway / RDM so that a stable origin is used (e.g., a fixed URL or fixed port), so that localStorage can persist across sessions?
If not, would it be possible to consider this as a feature request for the Gateway? Having a stable origin would solve the problem and allow web applications to properly persist user settings.
Thanks!