1 reply

It seems that passing of specific `x-

It seems that passing of specific

x-vercel-*

x-vercel-*

cf-*

cf-*

headers was triggering this. The headers were coming from

next/headers

next/headers

and may have gotten mixed around by all the trpc context switching going on in the T3stack boilerplate. If anyone runs into this I just wrote code to strip any of those headers being sent on UI requests

Communities Docs About Terms Privacy

It seems that passing of specific `x-

Similar Threads

It seems that passing of specific `x-

Similar Threads

Similar Threads

Similar Threads