Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix voice-call realtime WebSocket upgrades accept sibling stream paths

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

The voice-call realtime WebSocket upgrade router checks the request path with a raw startsWith(streamPath). With realtime.streamPath set to /voice/stream/realtime, a request to a sibling path like /voice/stream/realtime-extra/<token> is still routed into the realtime stream handler.

Root Cause

The configured stream path is the route boundary for realtime call media. Accepting sibling prefixes can confuse reverse-proxy or route-specific policy that expects only /voice/stream/realtime and slash-delimited children to reach the realtime handler.

Fix Action

Fix / Workaround

  1. Configure voice-call realtime with realtime.streamPath=/voice/stream/realtime.
  2. Send a WebSocket upgrade to /voice/stream/realtime/<token> and observe it reaches the realtime handler.
  3. Send a WebSocket upgrade to /voice/stream/realtime-extra/<token>.
RAW_BUFFERClick to expand / collapse

Summary

The voice-call realtime WebSocket upgrade router checks the request path with a raw startsWith(streamPath). With realtime.streamPath set to /voice/stream/realtime, a request to a sibling path like /voice/stream/realtime-extra/<token> is still routed into the realtime stream handler.

Why this matters

The configured stream path is the route boundary for realtime call media. Accepting sibling prefixes can confuse reverse-proxy or route-specific policy that expects only /voice/stream/realtime and slash-delimited children to reach the realtime handler.

Repro

  1. Configure voice-call realtime with realtime.streamPath=/voice/stream/realtime.
  2. Send a WebSocket upgrade to /voice/stream/realtime/<token> and observe it reaches the realtime handler.
  3. Send a WebSocket upgrade to /voice/stream/realtime-extra/<token>.

Expected: the sibling path is not treated as the realtime stream route.

Actual: the sibling path is routed into the realtime handler because /voice/stream/realtime-extra/<token>.startsWith(/voice/stream/realtime) is true.

Suggested fix

Match the configured path exactly or require the next character to be /, so only /voice/stream/realtime and /voice/stream/realtime/<token> are accepted.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#model save/load#optimization#mixed precision#training loop#device allocation

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix voice-call realtime WebSocket upgrades accept sibling stream paths