http.globalAgent Global instance of Agent which is used as the default for all http client requests.

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: http.ClientRequest This object is created internally and returned from http.request(). It represents an in-progress request whose header has already been queued. The header is still mutable using the setHeader(name, value), getHeader(name), removeHeader(name) API. The actual header will be sent along with the first data chunk or when closing the connection. To get the response, add a listener for 'response' to the request object. 'response' will be emitted from the request object when t

http.get(options[, callback]) Since most requests are GET requests without bodies, Node.js provides this convenience method. The only difference between this method and http.request() is that it sets the method to GET and calls req.end() automatically. Example: http.get('http://www.google.com/index.html', (res) => { console.log(`Got response: ${res.statusCode}`); // consume response body res.resume(); }).on('error', (e) => { console.log(`Got error: ${e.message}`); });

http.createServer([requestListener]) Returns a new instance of http.Server. The requestListener is a function which is automatically added to the 'request' event.

http.createClient([port][, host]) Stability: 0 - Deprecated: Use http.request() instead. Constructs a new HTTP client. port and host refer to the server to be connected to.

Class: http.Agent The HTTP Agent is used for pooling sockets used in HTTP client requests. The HTTP Agent also defaults client requests to using Connection:keep-alive. If no pending HTTP requests are waiting on a socket to become free the socket is closed. This means that Node.js's pool has the benefit of keep-alive when under load but still does not require developers to manually close the HTTP clients using KeepAlive. If you opt into using HTTP KeepAlive, you can create an Agent object with

hmac.update(data[, input_encoding]) Updates the Hmac content with the given data, the encoding of which is given in input_encoding and can be 'utf8', 'ascii' or 'binary'. If encoding is not provided, and the data is a string, an encoding of 'utf8' is enforced. If data is a Buffer then input_encoding is ignored. This can be called many times with new data as it is streamed.

hmac.digest([encoding]) Calculates the HMAC digest of all of the data passed using hmac.update(). The encoding can be 'hex', 'binary' or 'base64'. If encoding is provided a string is returned; otherwise a Buffer is returned; The Hmac object can not be used again after hmac.digest() has been called. Multiple calls to hmac.digest() will result in an error being thrown.

Class: Hmac The Hmac Class is a utility for creating cryptographic HMAC digests. It can be used in one of two ways: As a stream that is both readable and writable, where data is written to produce a computed HMAC digest on the readable side, or Using the hmac.update() and hmac.digest() methods to produce the computed HMAC digest. The crypto.createHmac() method is used to create Hmac instances. Hmac objects are not to be created directly using the new keyword. Example: Using Hmac objects as