Net

<!--introduced_in=v0.10.0-->

<!--lint disable maximum-line-length-->

Stability: 2 - Stable

<!-- source_link=lib/net.js -->

The node:net module provides an asynchronous network API for creating stream-based TCP or [IPC][] servers ([net.createServer()][]) and clients ([net.createConnection()][]).

It can be accessed using:

import net from 'node:net';
const net = require('node:net');

IPC support

<!-- YAML changes: - version: v20.8.0 pr-url: https://github.com/nodejs/node/pull/49667 description: Support binding to abstract Unix domain socket path like \0abstract. We can bind '\0' for Node.js < v20.4.0. -->

The node:net module supports IPC with named pipes on Windows, and Unix domain sockets on other operating systems.

Identifying paths for IPC connections

[net.connect()][], [net.createConnection()][], [server.listen()][], and [socket.connect()][] take a path parameter to identify IPC endpoints.

On Unix, the local domain is also known as the Unix domain. The path is a file system pathname. It will throw an error when the length of pathname is greater than the length of sizeof(sockaddr_un.sun_path). Typical values are 107 bytes on Linux and 103 bytes on macOS. If a Node.js API abstraction creates the Unix domain socket, it will unlink the Unix domain socket as well. For example, [net.createServer()][] may create a Unix domain socket and [server.close()][] will unlink it. But if a user creates the Unix domain socket outside of these abstractions, the user will need to remove it. The same applies when a Node.js API creates a Unix domain socket but the program then crashes. In short, a Unix domain socket will be visible in the file system and will persist until unlinked. On Linux, You can use Unix abstract socket by adding \0 to the beginning of the path, such as \0abstract. The path to the Unix abstract socket is not visible in the file system and it will disappear automatically when all open references to the socket are closed.

On Windows, the local domain is implemented using a named pipe. The path must refer to an entry in \\?\pipe\ or \\.\pipe\. Any characters are permitted, but the latter may do some processing of pipe names, such as resolving .. sequences. Despite how it might look, the pipe namespace is flat. Pipes will not persist. They are removed when the last reference to them is closed. Unlike Unix domain sockets, Windows will close and remove the pipe when the owning process exits.

JavaScript string escaping requires paths to be specified with extra backslash escaping such as:

net.createServer().listen(
  path.join('\\\\?\\pipe', process.cwd(), 'myctl'));

Class: net.BlockList

<!-- YAML added: - v15.0.0 - v14.18.0 -->

The BlockList object can be used with some network APIs to specify rules for disabling inbound or outbound access to specific IP addresses, IP ranges, or IP subnets.

blockList.addAddress(address[, type])

<!-- YAML added: - v15.0.0 - v14.18.0 -->

  • address {string|net.SocketAddress} An IPv4 or IPv6 address.
  • type {string} Either 'ipv4' or 'ipv6'. Default: 'ipv4'.

Adds a rule to block the given IP address.

blockList.addAddresses(addresses[, type])

<!-- YAML added: v26.8.0 -->

  • addresses {string[]|net.SocketAddress[]} An array of IPv4 or IPv6 addresses.
  • type {string} Either 'ipv4' or 'ipv6'. Default: 'ipv4'.

Adds multiple address rules to the block list in a single operation. This is more efficient than calling blockList.addAddress() repeatedly when adding a large number of individual addresses, as the addresses are inserted under a single internal lock acquisition.

blockList.addCIDR(cidr)

<!-- YAML added: v26.8.0 -->

  • cidr {string} An IPv4 or IPv6 subnet in CIDR notation (e.g. '10.0.0.0/8' or '2001:db8::/32').

Adds a subnet rule using CIDR notation. The address family is automatically detected from the address (IPv6 if the address contains ':', IPv4 otherwise). This is equivalent to calling blockList.addSubnet() with the parsed network address, prefix length, and family.

blockList.addCIDRs(cidrs)

<!-- YAML added: v26.8.0 -->

  • cidrs {string[]} An array of IPv4 or IPv6 subnets in CIDR notation.

Adds multiple subnet rules using CIDR notation in a single call. The address family for each entry is automatically detected. This is equivalent to calling blockList.addCIDR() for each element of the array.

blockList.addRange(start, end[, type])

<!-- YAML added: - v15.0.0 - v14.18.0 -->

  • start {string|net.SocketAddress} The starting IPv4 or IPv6 address in the range.
  • end {string|net.SocketAddress} The ending IPv4 or IPv6 address in the range.
  • type {string} Either 'ipv4' or 'ipv6'. Default: 'ipv4'.

Adds a rule to block a range of IP addresses from start (inclusive) to end (inclusive).

blockList.addSubnet(net, prefix[, type])

<!-- YAML added: - v15.0.0 - v14.18.0 -->

  • net {string|net.SocketAddress} The network IPv4 or IPv6 address.
  • prefix {number} The number of CIDR prefix bits. For IPv4, this must be a value between 0 and 32. For IPv6, this must be between 0 and 128.
  • type {string} Either 'ipv4' or 'ipv6'. Default: 'ipv4'.

Adds a rule to block a range of IP addresses specified as a subnet mask.

blockList.check(address[, type])

<!-- YAML added: - v15.0.0 - v14.18.0 -->

  • address {string|net.SocketAddress} The IP address to check
  • type {string} Either 'ipv4' or 'ipv6'. Default: 'ipv4'.
  • Returns: {boolean}

Returns true if the given IP address matches any of the rules added to the BlockList.

const blockList = new net.BlockList();
blockList.addAddress('123.123.123.123');
blockList.addRange('10.0.0.1', '10.0.0.10');
blockList.addSubnet('8592:757c:efae:4e45::', 64, 'ipv6');

console.log(blockList.check('123.123.123.123'));  // Prints: true
console.log(blockList.check('10.0.0.3'));  // Prints: true
console.log(blockList.check('222.111.111.222'));  // Prints: false

// IPv6 notation for IPv4 addresses works:
console.log(blockList.check('::ffff:7b7b:7b7b', 'ipv6')); // Prints: true
console.log(blockList.check('::ffff:123.123.123.123', 'ipv6')); // Prints: true

blockList.clear()

<!-- added: v26.8.0 -->

Clears all rules from the BlockList.

blockList.fromJSON(value)

Stability: 1.2 - Release candidate

<!-- YAML added: - v24.5.0 - v22.19.0 -->

const blockList = new net.BlockList();
const data = [
  'Subnet: IPv4 192.168.1.0/24',
  'Address: IPv4 10.0.0.5',
  'Range: IPv4 192.168.2.1-192.168.2.10',
  'Range: IPv4 10.0.0.1-10.0.0.10',
];
blockList.fromJSON(data);
blockList.fromJSON(JSON.stringify(data));
  • value Blocklist.rules

BlockList.isBlockList(value)

<!-- YAML added: - v23.4.0 - v22.13.0 -->

  • value {any} Any JS value
  • Returns {boolean} true if the value is a net.BlockList.

BlockList.PRIVATE_RANGES

<!-- YAML added: v26.8.0 -->

  • Type: {string[]}

A frozen array of CIDR strings representing private, loopback, and link-local IP address ranges. This can be passed to blockList.addCIDRs() to quickly populate a blocklist with all non-routable address ranges.

The included ranges are:

  • 10.0.0.0/8 — RFC 1918 private IPv4
  • 172.16.0.0/12 — RFC 1918 private IPv4
  • 192.168.0.0/16 — RFC 1918 private IPv4
  • 127.0.0.0/8 — IPv4 loopback
  • ::1/128 — IPv6 loopback
  • 169.254.0.0/16 — IPv4 link-local
  • fe80::/10 — IPv6 link-local
  • fc00::/7 — IPv6 unique local (ULA)
const blockList = new net.BlockList();
blockList.addCIDRs(net.BlockList.PRIVATE_RANGES);

console.log(blockList.check('10.0.0.1'));      // Prints: true
console.log(blockList.check('127.0.0.1'));     // Prints: true
console.log(blockList.check('8.8.8.8'));       // Prints: false

blockList.removeAddress(address[, type])

<!-- YAML added: v26.8.0 -->

  • address {string|net.SocketAddress} An IPv4 or IPv6 address.
  • type {string} Either 'ipv4' or 'ipv6'. Default: 'ipv4'.

Removes a rule that was previously added with blockList.addAddress(). The address must match exactly the value used when the rule was added. If the specified address does not exist, this is a no-op.

blockList.removeCIDR(cidr)

<!-- YAML added: v26.8.0 -->

  • cidr {string} An IPv4 or IPv6 subnet in CIDR notation (e.g. '10.0.0.0/8' or '2001:db8::/32').

Removes a subnet rule using CIDR notation. The address family is automatically detected from the address. This is equivalent to calling blockList.removeSubnet() with the parsed network address, prefix length, and family. If the specified subnet does not exist, this is a no-op.

blockList.removeRange(start, end[, type])

<!-- YAML added: v26.8.0 -->

  • start {string|net.SocketAddress} The starting IPv4 or IPv6 address in the range.
  • end {string|net.SocketAddress} The ending IPv4 or IPv6 address in the range.
  • type {string} Either 'ipv4' or 'ipv6'. Default: 'ipv4'.

Removes a rule that was previously added with blockList.addRange(). The start and end addresses must match exactly the values used when the rule was added. If the specified range does not exist, this is a no-op.

blockList.removeSubnet(net, prefix[, type])

<!-- YAML added: v26.8.0 -->

  • net {string|net.SocketAddress} The network IPv4 or IPv6 address.
  • prefix {number} The number of CIDR prefix bits. For IPv4, this must be a value between 0 and 32. For IPv6, this must be between 0 and 128.
  • type {string} Either 'ipv4' or 'ipv6'. Default: 'ipv4'.

Removes a rule that was previously added with blockList.addSubnet(). The network address and prefix must match exactly the values used when the rule was added. If the specified subnet does not exist, this is a no-op.

blockList.rules

<!-- YAML added: - v15.0.0 - v14.18.0 -->

  • Type: {string[]}

The list of rules added to the blocklist.

blockList.size

<!-- YAML added: v26.8.0 -->

  • Type: {number}

The number of rules in the blocklist. This is equivalent to blockList.rules.length but does not allocate the rules array.

blockList.toJSON()

Stability: 1.2 - Release candidate

<!-- YAML added: - v24.5.0 - v22.19.0 -->

  • Returns Blocklist.rules

Class: net.SocketAddress

<!-- YAML added: - v15.14.0 - v14.18.0 -->

new net.SocketAddress([options])

<!-- YAML added: - v15.14.0 - v14.18.0 -->

  • options {Object}
  • address {string} The network address as either an IPv4 or IPv6 string. Default: '127.0.0.1' if family is 'ipv4'; '::' if family is 'ipv6'.
  • family {string} One of either 'ipv4' or 'ipv6'. Default: 'ipv4'.
  • flowlabel {number} An IPv6 flow-label used only if family is 'ipv6'.
  • port {number} An IP port.

socketaddress.address

<!-- YAML added: - v15.14.0 - v14.18.0 -->

  • Type: {string}

socketaddress.family

<!-- YAML added: - v15.14.0 - v14.18.0 -->

  • Type: {string} Either 'ipv4' or 'ipv6'.

socketaddress.flowlabel

<!-- YAML added: - v15.14.0 - v14.18.0 -->

  • Type: {number}

socketaddress.port

<!-- YAML added: - v15.14.0 - v14.18.0 -->

  • Type: {number}

SocketAddress.parse(input)

<!-- YAML added: - v23.4.0 - v22.13.0 -->

  • input {string} An input string containing an IP address and optional port, e.g. 123.1.2.3:1234 or [1::1]:1234.
  • Returns: {net.SocketAddress} Returns a SocketAddress if parsing was successful. Otherwise returns undefined.

Class: net.Server

<!-- YAML added: v0.1.90 -->

  • Extends: {EventEmitter}

This class is used to create a TCP or [IPC][] server.

A listening TCP net.Server can be transferred to a worker thread by listing it in the transferList of a [worker_threads][] postMessage() call. This moves the underlying listening socket to the receiving thread, where it resumes accepting connections. See [Transferring TCP handles to other threads][].

new net.Server([options][, connectionListener])

  • options {Object} See [net.createServer([options][, connectionListener])][net.createServer()].
  • connectionListener {Function} Automatically set as a listener for the ['connection'][] event.
  • Returns: {net.Server}

net.Server is an [EventEmitter][] with the following events:

Event: 'close'

<!-- YAML added: v0.5.0 -->

Emitted when the server closes. If connections exist, this event is not emitted until all connections are ended.

Event: 'connection'

<!-- YAML added: v0.1.90 -->

  • Type: {net.Socket} The connection object

Emitted when a new connection is made. socket is an instance of net.Socket.

Event: 'error'

<!-- YAML added: v0.1.90 -->

  • Type: {Error}

Emitted when an error occurs. Unlike [net.Socket][], the ['close'][] event will not be emitted directly following this event unless [server.close()][] is manually called. See the example in discussion of [server.listen()][].

Event: 'listening'

<!-- YAML added: v0.1.90 -->

Emitted when the server has been bound after calling [server.listen()][].

Event: 'drop'

<!-- YAML added: - v18.6.0 - v16.17.0 -->

When the number of connections reaches the threshold of server.maxConnections, the server will drop new connections and emit 'drop' event instead. If it is a TCP server, the argument is as follows, otherwise the argument is undefined.

  • data {Object} The argument passed to event listener.
  • localAddress {string} Local address.
  • localPort {number} Local port.
  • localFamily {string} Local family.
  • remoteAddress {string} Remote address.
  • remotePort {number} Remote port.
  • remoteFamily {string} Remote IP family. 'IPv4' or 'IPv6'.

server.address()

<!-- YAML added: v0.1.90 changes: - version: v18.4.0 pr-url: https://github.com/nodejs/node/pull/43054 description: The family property now returns a string instead of a number. - version: v18.0.0 pr-url: https://github.com/nodejs/node/pull/41431 description: The family property now returns a number instead of a string. -->

  • Returns: {Object|string|null}

Returns the bound address, the address family name, and port of the server as reported by the operating system if listening on an IP socket (useful to find which port was assigned when getting an OS-assigned address): { port: 12346, family: 'IPv4', address: '127.0.0.1' }.

For a server listening on a pipe or Unix domain socket, the name is returned as a string.

const server = net.createServer((socket) => {
  socket.end('goodbye\n');
}).on('error', (err) => {
  // Handle errors here.
  throw err;
});

// Grab an arbitrary unused port.
server.listen(() => {
  console.log('opened server on', server.address());
});

server.address() returns null before the 'listening' event has been emitted or after calling server.close().

server.close([callback])

<!-- YAML added: v0.1.90 -->

  • callback {Function} Called when the server is closed.
  • Returns: {net.Server}

Stops the server from accepting new connections and keeps existing connections. This function is asynchronous, the server is finally closed when all connections are ended and the server emits a ['close'][] event. The optional callback will be called once the 'close' event occurs. Unlike that event, it will be called with an Error as its only argument if the server was not open when it was closed.

server[Symbol.asyncDispose]()

<!-- YAML added: - v20.5.0 - v18.18.0 changes: - version: v24.2.0 pr-url: https://github.com/nodejs/node/pull/58467 description: No longer experimental. -->

Calls [server.close()][] and returns a promise that fulfills when the server has closed.

server.getConnections(callback)

<!-- YAML added: v0.9.7 -->

  • callback {Function}
  • Returns: {net.Server}

Asynchronously get the number of concurrent connections on the server. Works when sockets were sent to forks.

Callback should take two arguments err and count.

server.listen()

Start a server listening for connections. A net.Server can be a TCP or an [IPC][] server depending on what it listens to.

Possible signatures:

  • [server.listen(handle[, backlog][, callback])][server.listen(handle)]
  • [server.listen(options[, callback])][server.listen(options)]
  • [server.listen(path[, backlog][, callback])][server.listen(path)] for [IPC][] servers
  • [server.listen([port[, host[, backlog]]][, callback])][server.listen(port)] for TCP servers

This function is asynchronous. When the server starts listening, the ['listening'][] event will be emitted. The last parameter callback will be added as a listener for the ['listening'][] event.

All listen() methods can take a backlog parameter to specify the maximum length of the queue of pending connections. The actual length will be determined by the OS through sysctl settings such as tcp_max_syn_backlog and somaxconn on Linux. The default value of this parameter is 511 (not 512).

All [net.Socket][] are set to SO_REUSEADDR (see [socket(7)][] for details).

The server.listen() method can be called again if and only if there was an error during the first server.listen() call or server.close() has been called. Otherwise, an ERR_SERVER_ALREADY_LISTEN error will be thrown.

One of the most common errors raised when listening is EADDRINUSE. This happens when another server is already listening on the requested port/path/handle. One way to handle this would be to retry after a certain amount of time:

server.on('error', (e) => {
  if (e.code === 'EADDRINUSE') {
    console.error('Address in use, retrying...');
    setTimeout(() => {
      server.close();
      server.listen(PORT, HOST);
    }, 1000);
  }
});

server.listen(handle[, backlog][, callback])

<!-- YAML added: v0.5.10 -->

  • handle {Object}
  • backlog {number} Common parameter of [server.listen()][] functions
  • callback {Function}
  • Returns: {net.Server}

Start a server listening for connections on a given handle that has already been bound to a port, a Unix domain socket, or a Windows named pipe.

The handle object can be either a server, a socket (anything with an underlying _handle member), a [BoundSocket][], or an object with an fd member that is a valid file descriptor.

When handle is a [BoundSocket][], the server adopts the already-bound socket and starts listening on it. Adoption consumes the bound socket (see [ownership transfer][BoundSocket]).

Listening on a file descriptor is not supported on Windows.

server.listen(options[, callback])

<!-- YAML added: v0.11.14 changes: - version: - v23.1.0 - v22.12.0 pr-url: https://github.com/nodejs/node/pull/55408 description: The reusePort option is supported. - version: v15.6.0 pr-url: https://github.com/nodejs/node/pull/36623 description: AbortSignal support was added. - version: v11.4.0 pr-url: https://github.com/nodejs/node/pull/23798 description: The ipv6Only option is supported. -->

  • options {Object} Required. Supports the following properties:
  • backlog {number} Common parameter of [server.listen()][] functions.
  • exclusive {boolean} Default: false
  • handle {net.BoundSocket} A pre-bound [BoundSocket][]. The server adopts the already-bound socket and listens on it, ignoring host, port, and path. Adoption consumes the bound socket (see [ownership transfer][BoundSocket]).
  • host {string}
  • ipv6Only {boolean} For TCP servers, setting ipv6Only to true will disable dual-stack support, i.e., binding to host :: won't make 0.0.0.0 be bound. Default: false.
  • reusePort {boolean} For TCP servers, setting reusePort to true allows multiple sockets on the same host to bind to the same port. Incoming connections are distributed by the operating system to listening sockets. This option is available only on some platforms, such as Linux 3.9+, DragonFlyBSD 3.6+, FreeBSD 12.0+, Solaris 11.4, and AIX 7.2.5+. On unsupported platforms, this option raises an error. Default: false.
  • path {string} Will be ignored if port is specified. See [Identifying paths for IPC connections][].
  • port {number}
  • readableAll {boolean} For IPC servers makes the pipe readable for all users. Default: false.
  • signal {AbortSignal} An AbortSignal that may be used to close a listening server.
  • writableAll {boolean} For IPC servers makes the pipe writable for all users. Default: false.
  • callback {Function} functions.
  • Returns: {net.Server}

If handle is specified, the server adopts that pre-bound socket. Otherwise, if port is specified, it behaves the same as [server.listen([port[, host[, backlog]]][, callback])][server.listen(port)]. Otherwise, if path is specified, it behaves the same as [server.listen(path[, backlog][, callback])][server.listen(path)]. If none of them is specified, an error will be thrown.

Using the signal option to destroy a long-lived server as a resource cleanup mechanism is deprecated. The signal option remains appropriate for cancellation, externally propagated aborts, and timeouts. See [DEP0209](https://nodejs.org/docs/latest/api/deprecations.md#dep0209-using-abortsignal-to-dispose-of-resources.

If exclusive is false (default), then cluster workers will use the same underlying handle, allowing connection handling duties to be shared. When exclusive is true, the handle is not shared, and attempted port sharing results in an error. An example which listens on an exclusive port is shown below.

server.listen({
  host: 'localhost',
  port: 80,
  exclusive: true,
});

When exclusive is true and the underlying handle is shared, it is possible that several workers query a handle with different backlogs. In this case, the first backlog passed to the master process will be used.

Starting an IPC server as root may cause the server path to be inaccessible for unprivileged users. Using readableAll and writableAll will make the server accessible for all users.

If the signal option is enabled, calling .abort() on the corresponding AbortController is similar to calling .close() on the server:

const controller = new AbortController();
server.listen({
  host: 'localhost',
  port: 80,
  signal: controller.signal,
});
// Later, when you want to close the server.
controller.abort();

server.listen(path[, backlog][, callback])

<!-- YAML added: v0.1.90 -->

  • path {string} Path the server should listen to. See [Identifying paths for IPC connections][].
  • backlog {number} Common parameter of [server.listen()][] functions.
  • callback {Function}.
  • Returns: {net.Server}

Start an [IPC][] server listening for connections on the given path.

server.listen([port[, host[, backlog]]][, callback])

<!-- YAML added: v0.1.90 -->

  • port {number}
  • host {string}
  • backlog {number} Common parameter of [server.listen()][] functions.
  • callback {Function}.
  • Returns: {net.Server}

Start a TCP server listening for connections on the given port and host.

If port is omitted or is 0, the operating system will assign an arbitrary unused port, which can be retrieved by using server.address().port after the ['listening'][] event has been emitted.

If host is omitted, the server will accept connections on the [unspecified IPv6 address][] (::) when IPv6 is available, or the [unspecified IPv4 address][] (0.0.0.0) otherwise.

In most operating systems, listening to the [unspecified IPv6 address][] (::) may cause the net.Server to also listen on the [unspecified IPv4 address][] (0.0.0.0).

server.listening

<!-- YAML added: v5.7.0 -->

  • Type: {boolean} Indicates whether or not the server is listening for connections.

server.maxConnections

<!-- YAML added: v0.2.0 changes: - version: v21.0.0 pr-url: https://github.com/nodejs/node/pull/48276 description: Setting maxConnections to 0 drops all the incoming connections. Previously, it was interpreted as Infinity. -->

  • Type: {integer}

When the number of connections reaches the server.maxConnections threshold:

  1. If the process is not running in cluster mode, Node.js will close the connection.

  2. If the process is running in cluster mode, Node.js will, by default, route the connection to another worker process. To close the connection instead, set [server.dropMaxConnection][] to true.

It is not recommended to use this option once a socket has been sent to a child with [child_process.fork()][].

server.dropMaxConnection

<!-- YAML added: - v23.1.0 - v22.12.0 -->

  • Type: {boolean}

Set this property to true to begin closing connections once the number of connections reaches the [server.maxConnections][] threshold. This setting is only effective in cluster mode.

server.ref()

<!-- YAML added: v0.9.1 -->

  • Returns: {net.Server}

Opposite of unref(), calling ref() on a previously unrefed server will not let the program exit if it's the only server left (the default behavior). If the server is refed calling ref() again will have no effect.

server.unref()

<!-- YAML added: v0.9.1 -->

  • Returns: {net.Server}

Calling unref() on a server will allow the program to exit if this is the only active server in the event system. If the server is already unrefed calling unref() again will have no effect.

Class: net.Socket

<!-- YAML added: v0.3.4 -->

  • Extends: {stream.Duplex}

This class is an abstraction of a TCP socket or a streaming [IPC][] endpoint (uses named pipes on Windows, and Unix domain sockets otherwise). It is also an [EventEmitter][].

A net.Socket can be created by the user and used directly to interact with a server. For example, it is returned by [net.createConnection()][], so the user can use it to talk to the server.

It can also be created by Node.js and passed to the user when a connection is received. For example, it is passed to the listeners of a ['connection'][] event emitted on a [net.Server][], so the user can use it to interact with the client.

Transferring TCP handles to other threads

A connected TCP net.Socket can be moved to another thread by listing it in the transferList of a [worker_threads][] postMessage() call. After the transfer, the source socket is destroyed on the sending thread (further use fails with ERR_STREAM_DESTROYED rather than silently dropping data), and the socket continues to work on the receiving thread. This makes it possible to accept connections on one thread and distribute them across a pool of worker threads, for example to build a node:cluster-like model on top of worker threads.

The socket must be a freshly accepted or created TCP connection: it must still be attached to a live handle, must not be connecting or destroyed, and must not have started reading or have buffered data. Otherwise postMessage() throws ERR_WORKER_HANDLE_NOT_TRANSFERABLE. Only TCP sockets are supported.

const net = require('node:net');
const { Worker } = require('node:worker_threads');

// worker.js receives `{ socket }` messages and handles each connection.
const worker = new Worker('./worker.js');

const server = net.createServer((socket) => {
  // Hand the freshly accepted connection off to the worker thread.
  worker.postMessage({ socket }, [socket]);
});
server.listen(8000);

A listening [net.Server][] can be transferred the same way, which moves the listening socket itself (and its pending accept queue) to the receiving thread.

An un-adopted TCP [BoundSocket][] can also be transferred, which moves the bound (but not yet listening or connected) socket. This allows a port to be reserved synchronously on one thread and adopted by a server or outgoing connection on another. Pipe binds are not transferable. After the transfer, the source BoundSocket behaves as if it had been adopted: address(), fd() and close() throw [ERR_SOCKET_HANDLE_ADOPTED][].

new net.Socket([options])

<!-- YAML added: v0.3.4 changes: - version: v25.6.0 pr-url: https://github.com/nodejs/node/pull/61503 description: Added typeOfService option. - version: v15.14.0 pr-url: https://github.com/nodejs/node/pull/37735 description: AbortSignal support was added. - version: v12.10.0 pr-url: https://github.com/nodejs/node/pull/25436 description: Added onread option. -->

  • options {Object} Available options are:
  • allowHalfOpen {boolean} If set to false, then the socket will automatically end the writable side when the readable side ends. See [net.createServer()][] and the ['end'][] event for details. Default: false.
  • blockList {net.BlockList} blockList can be used for disabling outbound access to specific IP addresses, IP ranges, or IP subnets.
  • fd {number} If specified, wrap around an existing socket with the given file descriptor, otherwise a new socket will be created.
  • handle {net.BoundSocket} If specified, wrap around the bound socket from a [BoundSocket][]. A subsequent [socket.connect()][socket.connect()] uses the bound socket as the connection's source binding (honoring the bound local address and port). Adoption consumes the bound socket (see [ownership transfer][BoundSocket]).
  • keepAlive {boolean} If set to true, it enables keep-alive functionality on the socket immediately after the connection is established, similarly on what is done in [socket.setKeepAlive()][]. Default: false.
  • keepAliveInitialDelay {number} If set to a positive number, it sets the initial delay before the first keepalive probe is sent on an idle socket. Default: 0.
  • noDelay {boolean} If set to true, it disables the use of Nagle's algorithm immediately after the socket is established. Default: false.
  • onread {Object} If specified, incoming data is stored in a single buffer and passed to the supplied callback when data arrives on the socket. This will cause the streaming functionality to not provide any data. The socket will emit events like 'error', 'end', and 'close' as usual. Methods like pause() and resume() will also behave as expected.
    • buffer {Buffer|Uint8Array|Function} Either a reusable chunk of memory to use for storing incoming data or a function that returns such.
    • callback {Function} This function is called for every chunk of incoming data. Two arguments are passed to it: the number of bytes written to buffer and a reference to buffer. Return false from this function to implicitly pause() the socket. This function will be executed in the global context.
  • readable {boolean} Allow reads on the socket when an fd is passed, otherwise ignored. Default: false.
  • signal {AbortSignal} An Abort signal that may be used to destroy the socket.
  • typeOfService {number} The initial Type of Service (TOS) value.
  • writable {boolean} Allow writes on the socket when an fd is passed, otherwise ignored. Default: false.
  • Returns: {net.Socket}

Creates a new socket object.

The newly created socket can be either a TCP socket or a streaming [IPC][] endpoint, depending on what it [connect()][socket.connect()] to.

Event: 'close'

<!-- YAML added: v0.1.90 -->

  • hadError {boolean} true if the socket had a transmission error.

Emitted once the socket is fully closed. The argument hadError is a boolean which says if the socket was closed due to a transmission error.

Event: 'connect'

<!-- YAML added: v0.1.90 -->

Emitted when a socket connection is successfully established. See [net.createConnection()][].

Event: 'connectionAttempt'

<!-- YAML added: - v21.6.0 - v20.12.0 -->

  • ip {string} The IP which the socket is attempting to connect to.
  • port {number} The port which the socket is attempting to connect to.
  • family {number} The family of the IP. It can be 6 for IPv6 or 4 for IPv4.

Emitted when a new connection attempt is started. This may be emitted multiple times if the family autoselection algorithm is enabled in [socket.connect(options)][].

Event: 'connectionAttemptFailed'

<!-- YAML added: - v21.6.0 - v20.12.0 -->

  • ip {string} The IP which the socket attempted to connect to.
  • port {number} The port which the socket attempted to connect to.
  • family {number} The family of the IP. It can be 6 for IPv6 or 4 for IPv4.
  • error {Error} The error associated with the failure.

Emitted when a connection attempt failed. This may be emitted multiple times if the family autoselection algorithm is enabled in [socket.connect(options)][].

Event: 'connectionAttemptTimeout'

<!-- YAML added: - v21.6.0 - v20.12.0 -->

  • ip {string} The IP which the socket attempted to connect to.
  • port {number} The port which the socket attempted to connect to.
  • family {number} The family of the IP. It can be 6 for IPv6 or 4 for IPv4.

Emitted when a connection attempt timed out. This is only emitted (and may be emitted multiple times) if the family autoselection algorithm is enabled in [socket.connect(options)][].

Event: 'data'

<!-- YAML added: v0.1.90 -->

  • Type: {Buffer|string}

Emitted when data is received. The argument data will be a Buffer or String. Encoding of data is set by [socket.setEncoding()][].

The data will be lost if there is no listener when a Socket emits a 'data' event.

Event: 'drain'

<!-- YAML added: v0.1.90 -->

Emitted when the write buffer becomes empty. Can be used to throttle uploads.

See also: the return values of socket.write().

Event: 'end'

<!-- YAML added: v0.1.90 -->

Emitted when the other end of the socket signals the end of transmission, thus ending the readable side of the socket.

By default (allowHalfOpen is false) the socket will send an end of transmission packet back and destroy its file descriptor once it has written out its pending write queue. However, if allowHalfOpen is set to true, the socket will not automatically [end()][socket.end()] its writable side, allowing the user to write arbitrary amounts of data. The user must call [end()][socket.end()] explicitly to close the connection (i.e. sending a FIN packet back).

Event: 'error'

<!-- YAML added: v0.1.90 -->

  • Type: {Error}

Emitted when an error occurs. The 'close' event will be called directly following this event.

Event: 'lookup'

<!-- YAML added: v0.11.3 changes: - version: v5.10.0 pr-url: https://github.com/nodejs/node/pull/5598 description: The host parameter is supported now. -->

Emitted after resolving the host name but before connecting. Not applicable to Unix sockets.

  • err {Error|null} The error object. See [dns.lookup()][].
  • address {string} The IP address.
  • family {number|null} The address type. See [dns.lookup()][].
  • host {string} The host name.

Event: 'ready'

<!-- YAML added: v9.11.0 -->

Emitted when a socket is ready to be used.

Triggered immediately after 'connect'.

Event: 'timeout'

<!-- YAML added: v0.1.90 -->

Emitted if the socket times out from inactivity. This is only to notify that the socket has been idle. The user must manually close the connection.

See also: [socket.setTimeout()][].

socket.address()

<!-- YAML added: v0.1.90 changes: - version: v18.4.0 pr-url: https://github.com/nodejs/node/pull/43054 description: The family property now returns a string instead of a number. - version: v18.0.0 pr-url: https://github.com/nodejs/node/pull/41431 description: The family property now returns a number instead of a string. -->

  • Returns: {Object}

Returns the bound address, the address family name and port of the socket as reported by the operating system: { port: 12346, family: 'IPv4', address: '127.0.0.1' }

socket.autoSelectFamilyAttemptedAddresses

<!-- YAML added: - v19.4.0 - v18.18.0 -->

  • Type: {string[]}

This property is only present if the family autoselection algorithm is enabled in [socket.connect(options)][] and it is an array of the addresses that have been attempted.

Each address is a string in the form of $IP:$PORT. If the connection was successful, then the last address is the one that the socket is currently connected to.

socket.bufferSize

<!-- YAML added: v0.3.8 deprecated: - v14.6.0 -->

Stability: 0 - Deprecated: Use [writable.writableLength][] instead.

  • Type: {integer}

This property shows the number of characters buffered for writing. The buffer may contain strings whose length after encoding is not yet known. So this number is only an approximation of the number of bytes in the buffer.

net.Socket has the property that socket.write() always works. This is to help users get up and running quickly. The computer cannot always keep up with the amount of data that is written to a socket. The network connection simply might be too slow. Node.js will internally queue up the data written to a socket and send it out over the wire when it is possible.

The consequence of this internal buffering is that memory may grow. Users who experience large or growing bufferSize should attempt to “throttle” the data flows in their program with [socket.pause()][] and [socket.resume()][].

socket.bytesRead

<!-- YAML added: v0.5.3 -->

  • Type: {integer}

The amount of received bytes.

socket.bytesWritten

<!-- YAML added: v0.5.3 -->

  • Type: {integer}

The amount of bytes sent.

socket.connect()

Initiate a connection on a given socket.

Possible signatures:

  • [socket.connect(options[, connectListener])][socket.connect(options)]
  • [socket.connect(path[, connectListener])][socket.connect(path)] for [IPC][] connections.
  • [socket.connect(port[, host][, connectListener])][socket.connect(port)] for TCP connections.
  • Returns: {net.Socket} The socket itself.

This function is asynchronous. When the connection is established, the ['connect'][] event will be emitted. If there is a problem connecting, instead of a ['connect'][] event, an ['error'][] event will be emitted with the error passed to the ['error'][] listener. The last parameter connectListener, if supplied, will be added as a listener for the ['connect'][] event once.

This function should only be used for reconnecting a socket after 'close' has been emitted or otherwise it may lead to undefined behavior.

socket.connect(options[, connectListener])

<!-- YAML added: v0.1.90 changes: - version: - v20.0.0 - v18.18.0 pr-url: https://github.com/nodejs/node/pull/46790 description: The default value for the autoSelectFamily option is now true. The --enable-network-family-autoselection CLI flag has been renamed to --network-family-autoselection. The old name is now an alias but it is discouraged. - version: v19.4.0 pr-url: https://github.com/nodejs/node/pull/45777 description: The default value for autoSelectFamily option can be changed at runtime using setDefaultAutoSelectFamily or via the command line option --enable-network-family-autoselection. - version: - v19.3.0 - v18.13.0 pr-url: https://github.com/nodejs/node/pull/44731 description: Added the autoSelectFamily option. - version: - v17.7.0 - v16.15.0 pr-url: https://github.com/nodejs/node/pull/41310 description: The noDelay, keepAlive, and keepAliveInitialDelay options are supported now. - version: v6.0.0 pr-url: https://github.com/nodejs/node/pull/6021 description: The hints option defaults to 0 in all cases now. Previously, in the absence of the family option it would default to dns.ADDRCONFIG | dns.V4MAPPED. - version: v5.11.0 pr-url: https://github.com/nodejs/node/pull/6000 description: The hints option is supported now. -->

  • options {Object}
  • connectListener {Function} Common parameter of [socket.connect()][] methods. Will be added as a listener for the ['connect'][] event once.
  • Returns: {net.Socket} The socket itself.

Initiate a connection on a given socket. Normally this method is not needed, the socket should be created and opened with [net.createConnection()][]. Use this only when implementing a custom Socket.

For TCP connections, available options are:

  • autoSelectFamily {boolean}: If set to true, it enables a family autodetection algorithm that loosely implements section 5 of [RFC 8305][]. The all option passed to lookup is set to true and the sockets attempts to connect to all obtained IPv6 and IPv4 addresses, in sequence, until a connection is established. The first returned AAAA address is tried first, then the first returned A address, then the second returned AAAA address and so on. Each connection attempt (but the last one) is given the amount of time specified by the autoSelectFamilyAttemptTimeout option before timing out and trying the next address. Ignored if the family option is not 0 or if localAddress is set. Connection errors are not emitted if at least one connection succeeds. If all connections attempts fails, a single AggregateError with all failed attempts is emitted. Default: [net.getDefaultAutoSelectFamily()][].
  • autoSelectFamilyAttemptTimeout {number}: The amount of time in milliseconds to wait for a connection attempt to finish before trying the next address when using the autoSelectFamily option. If set to a positive integer less than 10, then the value 10 will be used instead. Default: [net.getDefaultAutoSelectFamilyAttemptTimeout()][].
  • family {number}: Version of IP stack. Must be 4, 6, or 0. The value 0 indicates that both IPv4 and IPv6 addresses are allowed. Default: 0.
  • hints {number} Optional [dns.lookup() hints][].
  • host {string} Host the socket should connect to. Default: 'localhost'.
  • localAddress {string} Local address the socket should connect from.
  • localPort {number} Local port the socket should connect from.
  • lookup {Function} Custom lookup function. Default: [dns.lookup()][].
  • port {number} Required. Port the socket should connect to.

For [IPC][] connections, available options are:

  • path {string} Required. Path the client should connect to. See [Identifying paths for IPC connections][]. If provided, the TCP-specific options above are ignored.

socket.connect(path[, connectListener])

  • path {string} Path the client should connect to. See [Identifying paths for IPC connections][].
  • connectListener {Function} Common parameter of [socket.connect()][] methods. Will be added as a listener for the ['connect'][] event once.
  • Returns: {net.Socket} The socket itself.

Initiate an [IPC][] connection on the given socket.

Alias to [socket.connect(options[, connectListener])][socket.connect(options)] called with { path: path } as options.

socket.connect(port[, host][, connectListener])

<!-- YAML added: v0.1.90 -->

  • port {number} Port the client should connect to.
  • host {string} Host the client should connect to.
  • connectListener {Function} Common parameter of [socket.connect()][] methods. Will be added as a listener for the ['connect'][] event once.
  • Returns: {net.Socket} The socket itself.

Initiate a TCP connection on the given socket.

Alias to [socket.connect(options[, connectListener])][socket.connect(options)] called with {port: port, host: host} as options.

socket.connecting

<!-- YAML added: v6.1.0 -->

  • Type: {boolean}

If true, [socket.connect(options[, connectListener])][socket.connect(options)] was called and has not yet finished. It will stay true until the socket becomes connected, then it is set to false and the 'connect' event is emitted. Note that the [socket.connect(options[, connectListener])][socket.connect(options)] callback is a listener for the 'connect' event.

socket.destroy([error])

<!-- YAML added: v0.1.90 -->

  • error {Object}
  • Returns: {net.Socket}

Ensures that no more I/O activity happens on the current connection. Destroys the stream and closes the connection.

See [writable.destroy()][] for further details.

socket.destroyed

  • Type: {boolean} Indicates

(本文超出站点单文档体积上限,已截断)