Chris Tate 7a5fdae1bd Send an http client request's head and body in one write ...

request.end(body) on a request whose head was not sent yet wrote the
head and then the body. On a socket that was already connected (a
reused keep-alive connection), each write is sent at once, so the two
went out as separate segments, and the server could handle the head and
answer before the body arrived. Node sends the head together with the
body. When the client and the server run in one program, the server's
'end' and 'close' for the request and the client's reading of the
response then depended on which socket the poller reported first: corpus
5409-http-held-request-body printed the client's line before the
request's 'end' and 'close' in a macOS dev build.

The head and a body known at end() now go out as one write, as Node
sends them (the server's response already did).

2026-10-22 16:45:59 -05:00

..

src

Send an http client request's head and body in one write

2026-10-22 16:45:59 -05:00

test

Support the legacy createCipheriv modes and crypto.checkPrime/generatePrime (#1832)

2026-10-22 16:32:12 -05:00

vendor

Support asymmetric keys, signatures and Ed25519 in node:crypto and WebCrypto

2026-10-22 02:49:33 -05:00

LICENSE

init

2026-07-22 18:08:04 -05:00

package.json

Prepare v0.4.2 release

2026-10-22 11:14:27 -05:00