Showing data dump in the type text/x-component on the UI

[nandap4790]

Summary

When I do a client side navigation from Page A to Page B using Link component, the page renders correctly.
When I check the network request, the type of the content being text/x-component and the response being:

0:[["children",["slug","/slug","oc"], in this format.

Now when I refresh the page, I get:
0:[["children",["slug","/slug","oc"], being dumped on the UI in place of HTML.

I suspect this to be a cache issue, because when a query param is added the page renders perfectly and when I bypass the cache it renders correctly.

This does not happen there is a server navigation.

Can someone shed some light on this ?

Additional information

No response

Example

No response

[jihu]

Hi,

We are actually struggling with the same problem. Turns out that Next.js does some magic with the "vary" header, which instructs caching layers/services how to cache the content. If your caching layer, like a CDN, doesn't handle the vary header, or handles it incorrectly, then this can happen. I'm haven't found any official documentation on this, but I found this discussion that might help you:

https://www.reddit.com/r/nextjs/comments/13bizz0/hosting_ssr_site_with_cache_control/

[cizz3007]

I am experiencing this problem.
I'm hoping for a solution soon.

[vinizinmoraes]

Were you able to find a solution for this issue? We are having this problem with cloudfare caching.

[Protino]

Would disabling text/x-component content type on CDN resolve this issue?

Were you able to find any solution?

[shockbs]

I'm looking for a solution too! It serves either text/x-component or application/octet-stream with a rsc txt content instead of html :(
and i have to clear cache for that path on cloudflare to fix it, every time for every single page

[yongshun950824]

Having the same isue as well. But for my case it happens after migrate from CloudFlare to Imperva. And previously in CloudFlare, not face this issue. As I know the attempt that managed by infra & Imperva team is to disable caching for certain URL path/whole website, this issue is "temporary" resolved, but they mentioned that this is not a good approach.

[Protino]

Since we use Akamai, we solved this by just disabling 'Remove vary header'

[seloElo]

Found out I had the same issues on SSR pages! Had to remove the caching rule of thoses pages in cloudflare...