response.writeContinue() Sends a HTTP/1.1 100 Continue message to the client, indicating that the request body should be sent. See the 'checkContinue' event on Server.

response.getHeader(name) Reads out a header that's already been queued but not sent to the client. Note that the name is case insensitive. This can only be called before headers get implicitly flushed. Example: var contentType = response.getHeader('content-type');

Class: http.IncomingMessage An IncomingMessage object is created by http.Server or http.ClientRequest and passed as the first argument to the 'request' and 'response' event respectively. It may be used to access response status, headers and data. It implements the Readable Stream interface, as well as the following additional events, methods, and properties.

Class: stream.Transform Transform streams are Duplex streams where the output is in some way computed from the input. They implement both the Readable and Writable interfaces. Examples of Transform streams include: zlib streams crypto streams

util.isBoolean(object) Stability: 0 - Deprecated Returns true if the given "object" is a Boolean. Otherwise, returns false. const util = require('util'); util.isBoolean(1) // false util.isBoolean(0) // false util.isBoolean(false) // true

fs.fchownSync(fd, uid, gid) Synchronous fchown(2). Returns undefined.

server.close([callback]) See http.close() for details.

server.listen(handle[, callback])

tlsSocket.remoteFamily The string representation of the remote IP family. 'IPv4' or 'IPv6'.

Stability: 2 - Stable A stream is an abstract interface implemented by various objects in Node.js. For example a request to an HTTP server is a stream, as is process.stdout. Streams are readable, writable, or both. All streams are instances of EventEmitter. You can load the Stream base classes by doing require('stream'). There are base classes provided for Readable streams, Writable streams, Duplex streams, and Transform streams. This document is split up into 3 sections: The first section e