Certainly, adding that detail in English:
Subject: Encoding Issue with Cloudflare Worker after Recent Updates
Dear Cloudflare Support Team,
I hope this message finds you well.
Recently, I’ve been experiencing some character encoding issues with the worker I deployed on Cloudflare. The problem is intermittent, manifesting as garbled text occasionally. This inconsistency makes it challenging to pinpoint the exact cause. I wanted to note that I’m currently using wrangler version ^2.9.0. I wanted to reach out and ask if there have been any recent updates to the Cloudflare worker platform that might be affecting the behavior of deployed workers.
It would be greatly appreciated if you could provide some guidance on this issue and any potential solutions to rectify it.
Thank you for your time and assistance. I look forward to hearing from you soon.
Do you have a repro URL you can share and could you also possibly share the code around this too?
Also, are you fetching an origin here?
Thanks for getting back to me so quickly. I’m sorry, but due to confidentiality concerns, I can’t share the code right now. To give you some context, the worker does pull data from an origin, and that origin has Cloudflare’s proxy enabled. Everything was running smoothly with the code until August. I’ve also double-checked, and direct access to the origin seems fine. Do you have any insights or diagnostic steps I might consider to nail down the issue?
We just repro’d the issue ourselves a little bit ago. You can disable Brotli for now to solve it: Enable Brotli · Cloudflare Speed docs
We’ll let you know when we get it fixed
(Do you happen to have a ticket open? If so, what’s the ticket ID?)
Thanks for the quick response. Just to clarify, do I need to disable Brotli on both the origin and the worker routes?
The zone(s) which are impacted