service binding errors on OPTIONS Request

I have a worker that calls another passing a Request object. When it’s an OPTIONS Request, Cloudflare throws and exeption immediately. But still successfully runs the function in the 2nd worker. After some trial-and-error hacking, I found it’s due to the body: null. If I fabfricate a new Request object without a body, the errors go away. This was flooding our observability/logs with mystery errrors and quite annoying. Is this a bug in the Cloudflare RPC between service bindings?
0 Replies
No replies yetBe the first to reply to this messageJoin

Did you find this page helpful?