No content with body Debugging Lab

No content with bodyHTTP/APIEasyPreparing workspaceAutosaved

00:00

Incident Dossier

No content with body

Corporate proxies and some HTTP clients refuse responses that pair a 204 No Content status with a body. The audit record is convenient but the protocol contract forbids the combination, and the API gateway is logging client-side ECONNRESETs as a result.

Initial failing signal204 response carries a bodyExpected 204 with body=undefined · received 204 with body={deletedId, deletedAt}

Progress

1Reproduce the bugRun checks

2Edit the fixOpen

3Pass checksOpen

4Submit fixOpen

Reproduction Steps

Run npm test.
Inspect the failing assertion about the DELETE response body.
Decide whether the response should be 204 (no body) or 200 (with body).
Adjust the response builder so 204 carries no body.

Focus Mode

Start

src/api.js

Likely area

src/api.js

Progressive hints

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

TopicHTTP/API

DifficultyEasy

Est. time10 min

Workspacecreating

Explorer

Preparing workspace 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$ workspace boot

Workspace booting...