It seems that passing of specific `x-
It seems that passing of specific
x-vercel-* or cf-* headers was triggering this. The headers were coming from 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 requests2 Replies
hi @Jeff 👋
could you share more details on your setup and issue? I'm wondering if we should document this as a gotcha people can encounter (or if it is a very edge case scenario)
Hello, I inherited this project from a client that probably broke some no-nos, but basically we were using:
https://create.t3.gg/
in nextjs app dir
and this
headers() call was returning a header cf-connecting-ip that was problematic, as Erisa pointed out in the main channel.
Unclear to me why, maybe something server components related, or maybe that shouldn't have been passed "headers" obj on the UI side.
Because of this, the requests from the UI to x.pages.dev was blocked on CF side, error code 1000
I wish I could provide more but am currently too busy