Ingress failed to proxy vnc

[xiaomao23zhi]

Description

I deployed opensandbox-server (v0.1.5) via Helm with gateway enabled and gatewayRouteMode set to "uri".
values.yaml

server:
   gateway:
    enabled: true
    gatewayRouteMode: "uri"
configToml: |
  [server]
  host = "0.0.0.0"
  port = 80
  log_level = "INFO"
  api_key = ""

  [runtime]
  type = "kubernetes"
  execd_image = "opensandbox/execd:v1.0.6"

  [kubernetes]
  kubeconfig_path = ""
  namespace = "opensandbox-system"
  informer_enabled = true
  informer_resync_seconds = 300
  informer_watch_timeout_seconds = 60
  workload_provider = "batchsandbox"
  batchsandbox_template_file = "/etc/opensandbox/example.batchsandbox-template.yaml"

  [storage]
  allowed_host_paths = []

After successfully create an AIO sandbox, I attempted to access VNC via:
http://my.example.com/sandboxes/{sandbox_id}/vnc/index.html?autoconnect=true

Observed Behavior

The VNC HTML page shows: Failed to connect to server.
The browser console shows that the noVNC page attempts to establish a WebSocket connection via ws://my.example.com/websockify, but I think it should be something like ws://my.example.com/{sandbox_id}/websockify?
The same issue occurs with code-server and terminal endpoint.

Expected Behavior

Does the OpenSandbox Ingress/gateway currently support proxying sandboxes with WebSocket-based services (e.g., noVNC, code-server, terminal)?