Open jmarioste opened 2 months ago
I believe that as you said, the error message only occurs on a proxy where the original url changes. I tested this on PlainProxies and there is no error through that proxy. However, the RSC fetch parameter is a hash that includes a header parameter called Next-Router-State-Tree which happens to be different from the original website and the proxied website.
Link to the code that reproduces this issue
https://github.com/jmarioste/test-proxy-app
To Reproduce
In our company, many of our customers are institutions and/or universities that uses proxy to access our app. We recently refactored our app to next 14 app router but seems to not hydrate and doesn't work when passed through their proxy (e.g., ezproxy). Error: Connection closed. is thrown. I can't post the exact details because of confidentiality. I'll just use google translate as an example. This doesn't happen when using the
/pages
directoryCurrent vs. Expected behavior
Current behavior:
Expected behavior:
Provide environment information
Which area(s) are affected? (Select all that apply)
Not sure
Which stage(s) are affected? (Select all that apply)
Vercel (Deployed), Other (Deployed)
Additional context
This doesn't happen on pages directory, only app directory using react server components.