serval
serval•9mo ago

HTTP 431: Input too long

Hi, we're using a complex query (multiple filters etc) with tRPC and react query integration. It happens, that the query is to big and the server returns a 431, due to http uri restrictions. There are some open PRs about this topic, but is there any workaround? We don't want to loose the useQuery semantics, so we don't want to change to mutation. Thanks
1 Reply
serval
serval•9mo ago
reported a bug for this: https://github.com/trpc/trpc/issues/4993
GitHub
bug: Too long input causes failure HTTP 431 · Issue #4993 · trpc/t...
Provide environment information System: OS: Linux 5.15 Ubuntu 20.04.4 LTS (Focal Fossa) CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz Memory: 12.16 GB / 15.55 GB Container: Yes Shell: 5.0....
More Posts
Function to release context post-batching?In our application every customer has their own schema, therefore we need a db client per request whforwarding headers in solidjsI have a setup with solidstart, and im trying to forward the client headeres to ttrpc. Here's my seSupport @tanstack/react-query 5.4.3will it support 5.4.3 @tanstack/react-query when i install above version with my next.js it unable tHelp with inferring output```ts return ctx.prisma.product.findMany({ include: { price: { select: { Would you recommend tRPC’s usage in this case?So we have two applications, one existing, one about to be started. These two applications will talkHow to limit payload size?Is there a way to limit the payload size? E.g., if a particularly large JSON payload is sent to the