We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
There is a bug in [email protected] causing responses to be aggressively buffered.
[email protected]
It breaks PPR in Next.js with wrangler dev - PPR works fine when deployed. See opennextjs/opennextjs-cloudflare#309
wrangler dev
I have a pretty good idea of the the root cause and how to fix that. I'll add more details here later this week and will submit a fix PR.
One workaround for now is to set the Content-Encoding of the response to identity (any value other than gzip or br should do).
Content-Encoding
identity
gzip
br
/cc @mhart @jasnell as we discussed it earlier
The text was updated successfully, but these errors were encountered:
I reported something similar a long time ago. Is this a same issue? #6577
Sorry, something went wrong.
@hi-ogawa this is probably the same root cause - I'll work on that probably early next week. Let's keep both issues opened until then.
Thanks!
vicb
No branches or pull requests
There is a bug in
[email protected]
causing responses to be aggressively buffered.It breaks PPR in Next.js with
wrangler dev
- PPR works fine when deployed.See opennextjs/opennextjs-cloudflare#309
I have a pretty good idea of the the root cause and how to fix that.
I'll add more details here later this week and will submit a fix PR.
One workaround for now is to set the
Content-Encoding
of the response toidentity
(any value other thangzip
orbr
should do)./cc @mhart @jasnell as we discussed it earlier
The text was updated successfully, but these errors were encountered: