Skip to content

Commit e14c32a

Browse files
committed
docs: fix proxied: false use cases to reflect HTTPS-only sandbox
1 parent 7752e62 commit e14c32a

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

docs/roo-code-cloud/environments.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -237,8 +237,8 @@ ports:
237237

238238
Use `proxied: false` only when the proxy layer itself is incompatible with your use case:
239239

240-
- **Direct socket access** for protocols that don't work through the HTTP proxy
241-
- **Non-HTTP services** that need the raw port exposed without any intermediary
240+
- **WebSocket or streaming connections** that are disrupted by the proxy intermediary
241+
- **Services with custom connection handling** that conflict with the proxy's request processing
242242

243243
:::warning[Warning]
244244
When `proxied` is `false`, the port is **completely exposed without authentication**, regardless of the `unauthenticated` setting. Non-proxied ports also count against a stricter limit (1 per environment vs. 10 for proxied ports). Only use this as a last resort when other options don't work.

0 commit comments

Comments
 (0)