fix: set correct "Content-Length" response header for special characters (#2045)

[ZeroCho]

• Fixes JSON response with special chars truncated since 2.2.0 #2045

@kettanaito
fyi, '안녕 세상', which has 13 bytes (4 Korean characters * 3b + 1b(space) === 13b), means 'hello world' in Korean.
{ firstName: '제로' } turns into {"firstName":"제로"} which has 22 bytes (16 ASCII characters + 2 Korean characters * 3b === 22b)

[technikhil314]

@kettanaito Can we have this merged? We too have some api that returns currency symbols which are special characters and the response is getting truncated because of this.

[ZeroCho]

@technikhil314 Until this PR gets merged, you have to manually set correct 'Content-Length' header for every response with special characters, for your response not to be truncated.

[Jesse1989pp]

@technikhil314 Until this PR gets merged, you have to manually set correct 'Content-Length' header for every response with special characters, for your response not to be truncated.

That drastically gave performance issues for us with a json response. We have a workaround with a text response including Content-Type': 'application/json; charset=utf8’ as a header.. 😅

[kettanaito]

This is great! Thank you for fixing this, @ZeroCho. 🚀

[kettanaito]

Released: v2.2.2 🎉

This has been released in v2.2.2!

• 📄 Release notes
• 📦 npm package

Make sure to always update to the latest version (npm i msw@latest) to get the newest features and bug fixes.

---

Predictable release automation by @ossjs/release.