Incident Dossier

Content-Type charset lie

Western-European customers see accented characters mangled in product descriptions. The bytes are correct on the wire; the client decoder labels them as UTF-8 even though the server honestly declared `charset=latin1`. The mismatch produces the classic Ã©-style mojibake on every page.

Initial failing signallatin1 body is decoded as UTF-8Expected behavior: decodeBody of a latin1 body returns 'café' · actual behavior: decodeBody returns 'caf' followed by U+FFFD replacement

Progress

1Reproduce the bugRun checks

2Edit the fixOpen

3Pass checksOpen

4Submit fixOpen

Reproduction Steps

Run npm test.
Inspect the failing assertion about the latin1 byte sequence 0x63 0x61 0x66 0xE9.
Trace which decoder the body is being passed through.
Honour the charset parameter from Content-Type.

Focus Mode

Start

src/decode.js

Likely area

src/decode.js

Challenge Coach

Hints reveal broad direction first, then narrow toward the suspect path without showing hidden tests or exact solution code.

TopicNetwork & Connectivity

DifficultyMedium

Est. time18 min

Workspacepreparing

Explorer

Loading files

Evidence Map

Failing signal loaded from challenge API
Workspace files loaded from workspace API
Results rendered only after API run/submit

Autosaved

workspace

Outputread-onlyready$ prepare workspace

Preparing workspace