Error: Cannot set headers after they are sent to client, occurs when trying to serve index.html, only occurs in v14.0.0 #756

abhimonk · 2021-10-23T17:18:47Z

Getting the following error when trying to go to the webpage returned by "npx http-server" serving my index.html:

Error [ERR_HTTP_HEADERS_SENT]: Cannot set headers after they are sent to the client

The issue does not occur if I use version 13.0.0

(See below for full stack trace)

If I repeat the reproduction steps with version 13.0.0, it works as expected.

Environment Versions

OS Type: Windows
Node version: 6.13.4
http-server version: 14.0.0

Steps to reproduce

Have just any index.html in your current folder
Run "npx http-server" from the current folder
Navigate to the URL returned (which should trigger serving your index.html)

Expected result

My index.html should be served and the contents of it should be displayed. This works fine in version 13.0.0.

Actual result

The server crashes with the following error:

[2021-10-23T17:10:29.869Z] "GET /" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/95.0.4638.54 Safari/537.36"
(node:3956) [DEP0066] DeprecationWarning: OutgoingMessage.prototype._headers is deprecated
_http_outgoing.js:485
throw new ERR_HTTP_HEADERS_SENT('set');

Error [ERR_HTTP_HEADERS_SENT]: Cannot set headers after they are sent to the client
at ServerResponse.setHeader (_http_outgoing.js:485:11)
at module.exports.ResponseStream. [as setHeader] (C:\Users\abhim\Documents\GameDev\JSDev\AttackAnimationGenerator\node_modules\union\lib\response-stream.js:100:34)
at Object.exports. (C:\Users\abhim\Documents\GameDev\JSDev\AttackAnimationGenerator\node_modules\http-server\lib\core\status-handlers.js:57:7)
at Readable. (C:\Users\abhim\Documents\GameDev\JSDev\AttackAnimationGenerator\node_modules\http-server\lib\core\index.js:339:22)
at Readable.emit (events.js:210:5)
at emitErrorNT (internal/streams/destroy.js:92:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:60:3)
code: 'ERR_HTTP_HEADERS_SENT'
}

Other information

I have seen the github issue #634, but it looks like their server is undergoing external traffic. I am just using my server for local testing with a simple index.html. This workflow worked fine in version 13.0.0, but when I switched to version 14.0.0 I get the above error.

natali27 · 2021-10-25T14:55:12Z

same problem with docker node:12.10.0-alpine ,
now needed to set version http-server@13.0.2 to fix this error

Ronkiro · 2021-10-29T15:12:35Z

+1, using node v12.14.0

totszwai · 2021-11-02T16:36:40Z

Came here for this, v14 is broken. Need to use 13.0.2...

boarwell · 2021-11-04T04:44:29Z

Reproduced this with Node.js v12.14.0, but not with v12.22.7 (the latest release of v12.x). As a workaround, could you update to the v12.22.7 (or higher)?

tutanck · 2021-11-04T15:23:47Z

Same problem here with docker node:12.11.1-alpine

wesleycsj · 2021-11-10T18:54:03Z

Problem is not with docker(or container versions), i faced same problem on ubuntu. http-server@14 is broken, need install 13.0.2 to get things working.

thornjad · 2021-12-06T20:56:36Z

Reproduced this with Node.js v12.14.0, but not with v12.22.7 (the latest release of v12.x). As a workaround, could you update to the v12.22.7 (or higher)?

This makes this sound like it may be a bug in Node, can anyone else confirm newer versions of Node work with http-server v14?

matthias-ccri · 2021-12-08T04:22:45Z

Seeing this on v12.13.1

srlowe · 2021-12-13T18:10:18Z

I'm seeing with v12.13.0

myleshk · 2021-12-20T09:04:30Z

Same here with v10.24.1

thornjad · 2021-12-20T18:17:05Z

I'm not currently able to reproduce this, tagging for help!

joshnoe · 2021-12-31T19:35:34Z

Can reproduce on node v12.14.1

systa · 2022-01-08T12:38:00Z

My node is v10.19.0 and I'm getting the same error. I will uninstall and search for other options.
Simple static http-server must be so simple, that things errors this never happens - regardless of node version.
Suggestion: simplify the code radically.

ThomasDEVio · 2022-01-17T20:18:20Z

Can reproduce on node v10.19.0, I updated to latest stable node, 16.13.2 and it works fine now!
https://phoenixnap.com/kb/update-node-js-version

zbynek · 2022-01-23T21:36:00Z

This is hiding another error

TypeError [ERR_INVALID_ARG_TYPE]: The first argument must be one of type string or Buffer. Received type number
    at write_ (_http_outgoing.js:618:11)
    at ServerResponse.write (_http_outgoing.js:586:15)
    at module.exports.ResponseStream.write (/root/http-server/node_modules/union/lib/response-stream.js:186:22)
    at Readable.ondata (_stream_readable.js:722:22)
    at Readable.emit (events.js:209:13)
    at addChunk (_stream_readable.js:305:12)
    at readableAddChunk (_stream_readable.js:286:11)
    at Readable.push (_stream_readable.js:220:10)
    at next (_stream_readable.js:1218:27)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)

and is happening since #736
@boarwell 's comment about failures on Node 10 probably applies to earlier versions of Node 12 too.

The issue can be reproduced with node (using alpine docker images) up to 12.15, it's OK in 12.16.

barryvdh · 2022-03-29T07:47:23Z

I ran into this issue with and old AngularJS project on MacOS. I just installed http-server and it didn't work. Forcing to v13 made it work without changes.

[Tue Mar 29 2022 09:43:48 GMT+0200 (Central European Summer Time)]  "GET /" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/98.0.4758.102 Safari/537.36"
_http_outgoing.js:470
    throw new ERR_HTTP_HEADERS_SENT('set');
    ^

Error [ERR_HTTP_HEADERS_SENT]: Cannot set headers after they are sent to the client
    at ServerResponse.setHeader (_http_outgoing.js:470:11)
    at module.exports.ResponseStream.(anonymous function) [as setHeader] (/Users/barry/Sites/app/node_modules/union/lib/response-stream.js:100:34)
    at Object.exports.(anonymous function) (/Users/barry/Sites/app/node_modules/http-server/lib/core/status-handlers.js:57:7)
    at Readable.stream.on (/Users/barry/Sites/app/node_modules/http-server/lib/core/index.js:339:22)
    at Readable.emit (events.js:198:13)
    at emitErrorNT (internal/streams/destroy.js:91:8)
    at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)
    at process._tickCallback (internal/process/next_tick.js:63:19)

github-actions · 2022-09-25T12:35:42Z

This issue has been inactive for 180 days

Ronkiro · 2022-09-30T21:19:13Z

bump, i think this still needs a solution

KissBalazs · 2023-04-04T16:39:45Z

Switching from node:10 to node:16 solved this issue for me.

abhimonk changed the title ~~Error: Cannot set headers after they are sent to client, occurs when trying to serve index.html, only occurs in v13.0.0~~ Error: Cannot set headers after they are sent to client, occurs when trying to serve index.html, only occurs in v14.0.0 Oct 23, 2021

Its-Just-Nans mentioned this issue Nov 14, 2021

Create a clean stream using fs.createReadStream #764

Open

9 tasks

thornjad added help-wanted high priority Very important bug or security fix labels Dec 20, 2021

JanMiksovsky mentioned this issue Jan 20, 2022

[Server crash error] running README example elix/react-example#12

Closed

zbynek mentioned this issue Jan 23, 2022

Make sure headers are not set twice on error #791

Merged

8 tasks

zbynek mentioned this issue Mar 4, 2022

Server Crashing with "Cannot set headers after they are sent to the client" #634

Open

chrisspen mentioned this issue Apr 8, 2022

Server crashes in the minimal example phiresky/sql.js-httpvfs#29

Closed

zbynek mentioned this issue Apr 8, 2022

Cannot set headers after they are sent to the client #805

Open

zbynek mentioned this issue Aug 9, 2022

Server crashes on starting #828

Closed

github-actions bot added the stale label Sep 25, 2022

github-actions bot removed the stale label Oct 1, 2022

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Error: Cannot set headers after they are sent to client, occurs when trying to serve index.html, only occurs in v14.0.0 #756

Error: Cannot set headers after they are sent to client, occurs when trying to serve index.html, only occurs in v14.0.0 #756

abhimonk commented Oct 23, 2021 •

edited

natali27 commented Oct 25, 2021

Ronkiro commented Oct 29, 2021 •

edited

totszwai commented Nov 2, 2021

boarwell commented Nov 4, 2021 •

edited

tutanck commented Nov 4, 2021

wesleycsj commented Nov 10, 2021 •

edited

thornjad commented Dec 6, 2021

matthias-ccri commented Dec 8, 2021

srlowe commented Dec 13, 2021

myleshk commented Dec 20, 2021

thornjad commented Dec 20, 2021

joshnoe commented Dec 31, 2021

systa commented Jan 8, 2022

ThomasDEVio commented Jan 17, 2022

zbynek commented Jan 23, 2022

barryvdh commented Mar 29, 2022

github-actions bot commented Sep 25, 2022

Ronkiro commented Sep 30, 2022

KissBalazs commented Apr 4, 2023 •

edited

Error: Cannot set headers after they are sent to client, occurs when trying to serve index.html, only occurs in v14.0.0 #756

Error: Cannot set headers after they are sent to client, occurs when trying to serve index.html, only occurs in v14.0.0 #756

Comments

abhimonk commented Oct 23, 2021 • edited

Environment Versions

Steps to reproduce

Expected result

Actual result

Other information

natali27 commented Oct 25, 2021

Ronkiro commented Oct 29, 2021 • edited

totszwai commented Nov 2, 2021

boarwell commented Nov 4, 2021 • edited

tutanck commented Nov 4, 2021

wesleycsj commented Nov 10, 2021 • edited

thornjad commented Dec 6, 2021

matthias-ccri commented Dec 8, 2021

srlowe commented Dec 13, 2021

myleshk commented Dec 20, 2021

thornjad commented Dec 20, 2021

joshnoe commented Dec 31, 2021

systa commented Jan 8, 2022

ThomasDEVio commented Jan 17, 2022

zbynek commented Jan 23, 2022

barryvdh commented Mar 29, 2022

github-actions bot commented Sep 25, 2022

Ronkiro commented Sep 30, 2022

KissBalazs commented Apr 4, 2023 • edited

abhimonk commented Oct 23, 2021 •

edited

Ronkiro commented Oct 29, 2021 •

edited

boarwell commented Nov 4, 2021 •

edited

wesleycsj commented Nov 10, 2021 •

edited

KissBalazs commented Apr 4, 2023 •

edited