mirror of
https://github.com/openclaw/openclaw.git
synced 2026-08-03 06:21:37 +00:00
151c549494
* fix(browser): resolve upload paths on the owning browser node, not the Gateway When a browser session is proxied to a remote node, the upload action previously ran resolveExistingUploadPaths on the Gateway, pinning paths to a filesystem the node cannot see and rejecting node-local files. The node-side /hooks/file-chooser route already re-resolves paths against its own filesystem, so skip Gateway-local resolution whenever the request is proxied and forward the requested paths as-is. Fixes openclaw/openclaw#115251 * fix(browser): transfer uploads to remote browser nodes * fix(browser): normalize upload abort errors --------- Co-authored-by: Vincent Koc <vincentkoc@ieee.org>
11 lines
581 B
TypeScript
11 lines
581 B
TypeScript
export const BROWSER_PROXY_COMMAND = "browser.proxy";
|
|
export const BROWSER_PROXY_UPLOAD_COMMAND = "browser.proxy.upload.v1";
|
|
|
|
export function browserProxyUploadUnavailableMessage(
|
|
pendingDeclaredCommands: readonly string[] | undefined,
|
|
): string {
|
|
return pendingDeclaredCommands?.includes(BROWSER_PROXY_UPLOAD_COMMAND)
|
|
? "browser node remote upload transfer is pending approval; approve the node's pending command update before retrying"
|
|
: "browser node does not support remote upload transfer; update the node or approve its pending command update before retrying";
|
|
}
|