Why are all RPC calls being sent as POST requests?

[melodyclue]

I’m using Next.js with oRPC and the TanStack integration. In my component, I call:

const { data, isPending, error } = useQuery(orpc.listProject.queryOptions())

However, even though I’m using useQuery, every request is issued as a POST instead of a GET. Is this the intended behavior of oRPC/TanStack integration, or am I missing some configuration?

[unnoq]

This can help you:

https://orpc.unnoq.com/docs/client/rpc-link#custom-request-method

#539

[melodyclue]

Thank you! It turns out I wasn’t actually sending GET requests at all—that was the root cause (#539).

One thing I’m still curious about: why does oRPC default to POST for all RPC calls? Frameworks like Hono or tRPC let you write GET as well, so I’m wondering what the reasoning is here.

[unnoq]

@melodyclue oRPC doesn't provide built-in hints for selecting GET or POST methods. In tRPC, you have .query and .mutation; in Hono, there’s .get, .post, etc. With oRPC, you'll need to instruct it explicitly using your own custom hints. More details here: https://orpc.unnoq.com/docs/client/rpc-link#custom-request-method