Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Ungzipping gzipped response from prerender service produces corrupted unicode strings

Open
#192 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
38/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
express, javascript
Domain
backend

Research direction

Start at index.js around line 213, where response chunks are converted to strings, and run the linked simple reproduction. Verify that handling split Unicode characters preserves the complete response, then confirm the reproduction no longer produces corrupted strings.

Written by the indexing model from the issue text.

Description

This is where bad things happens - if chunk contains only part of unicode character then implicit Buffer.toString() produces corrupted string.

The fix will be to keep an array of chunks and then invoking Buffer.concat(chunks).toString() at the end.

Simple repro with hotfix

Dominant language
JavaScript
Stars
921
Forks
185
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from prerender/prerender-node

All issues in prerender/prerender-node

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.