[eersnington]

• Send HTTP request bodies from the RivetKit client as bytes instead of a ReadableStream with duplex: "half". Since feat(http): stream HTTP bodies end-to-end #5516, action calls on a handle without .connect() failed in Safari, Firefox, and Chromium over HTTP/1.1.
• Read the body of a Request passed to handle.fetch() as bytes. Firefox has no Request.body, so the body was dropped.

// engine-client/actor-http-client.ts
const bytes = await actorRequest.arrayBuffer();
if (bytes.byteLength > 0) bodyToSend = bytes;
return fetch(gatewayUrl, { method, headers, body: bodyToSend, signal });

Runtime	Before	After
Node, Bun, Deno	works	works
Chromium, HTTP/2+	works	works
Chromium, HTTP/1.1	Failed to fetch	works
Safari / iOS	fails	works
Firefox	body dropped	works

[railway-app]

This PR was not deployed automatically as @eersnington does not have access to the Railway project.

In order to get automatic PR deploys, please add @eersnington to your workspace on Railway.

[claude]

Review

The fix is small and targeted. Buffering the body as bytes is the right approach for browsers. I found no blocking issues.

Observations

• No test coverage. The regression (HTTP/1.1 Chromium, Safari, Firefox) can't be caught by Node-only driver tests. A test that sends a Request with a body through sendHttpRequestToGateway and rawHttpFetch would help. It should cover a Request passed to handle.fetch() and one with an empty body, using real infrastructure.
• Streaming uploads are now buffered. Large or streaming request bodies are fully read into memory before sending. That is a reasonable tradeoff for browser compatibility, but a short note may be worth adding.
• readRequestBody abort behavior. Please confirm that an already-aborted signal rejects cleanly with an AbortError and leaves no unhandled rejection.
• Empty-body headers. When bytes.byteLength === 0, content-length and transfer-encoding are left in place. This is probably fine, but confirm a stale content-length can't mismatch.
• Duplicated GET/HEAD check. rawHttpFetch re-implements the method check that sendHttpRequestToGateway also has. This is minor.
• Style. The comments follow the repo conventions. Dropping the as RequestInit cast and duplex is a nice cleanup.

Overall this looks good to merge, with a regression test as a nice-to-have.

[the-company-company]

🟠 1 medium-severity finding

_{Reviewed commit 2ac03e0.}

[the-company-company]

✅ No issues found

_{Reviewed commit 275067c.}