tRPC•2y ago

v11 `Invalid Content-Type header`

The most recent update of v11 seems to break with:

Invalid Content-Type header. This request may not be supported by your tRPC Adapter, or possibly by tRPC at all

Invalid Content-Type header. This request may not be supported by your tRPC Adapter, or possibly by tRPC at all

The related commits in the rc.346 are probably:

I am using the react and vanilla fetch adapters, so according to the docs https://trpc.io/docs/migrate-from-v10-to-v11#explicit-content-type-checks-non-breaking my code should not be breaking

I went ahead and downgraded to

11.0.0-next-beta.318

11.0.0-next-beta.318

and it works fine

Alex / KATT 🐱•4/21/24, 7:03 AM

Cc @Nick Lucas

Alex / KATT 🐱•4/21/24, 7:04 AM

@jlarmst can you create an issue? Likely a bug

Nick•4/21/24, 7:14 AM

Yep a reproduction at very least woulds be super helpful

jlarmstOP•4/21/24, 8:52 AM

Thank you for the quick reply! It’s deeply tied to my personal project, but I will try to get a reproduction tomorrow

Jjlarmst Thank you for the quick reply! It’s deeply tied to my personal project, but I w...

Nick•4/21/24, 8:54 AM

Sure, for now you could give us an idea of what environment the issue is appearing in. Does it happen locally? Any reverse proxy etc? How are your links configured?

Nick•4/21/24, 8:55 AM

The header is mandatory for the first time now, so we're suspecting something non-vanilla in the mix

julius•4/21/24, 9:23 AM

Can you try when you have the chance @jlarmst - might fix things, or atleast give you a better error

jlarmstOP•4/21/24, 9:40 AM

Locally! Links are custom based on the SOA example because I’m trying out serverless with sst too. The only thing I wrote down to check tomorrow is that I’m setting custom headers and not setting a content-type

Jjlarmst Locally! Links are custom based on the SOA example because I’m trying out serve...

julius•4/21/24, 9:41 AM

yea that's probably the most likely reason. we currently require the content-type header to be set

jlarmstOP•4/21/24, 9:43 AM

I’ll try adding the to the defaultHeaders object I use with

jlarmstOP•4/21/24, 9:43 AM

So setting any headers means that the Content-Type must also be set manually, even when using the default clients

jlarmstOP•4/21/24, 9:58 AM

UPDATE: rc.347 did fix it. Manually setting a default header of works in rc.347, but not rc.346

jlarmstOP•4/21/24, 10:00 AM

Thank you everyone for your help!