Skip to main content

Utilizing HTTP/2 Push for Faster Page Load in Node.js

HTTP/2 has several advantages over HTTP/1 that I've mention in my earlier post. In this post, I want to show how push-request can be performed using Node.js to create an HTTP/2 server. Push request is used to push static files such as scripts and styles so that the client can consume those static files as soon as possible without the need to request them first.


In this example, several built-in Node modules are required and an external module for ease of content-type setting named mime. Let's install it first.

npm init
npm i --save mime

HTTP/2 encodes all headers of a request and it presents several new headers for identifying a request such as :method and :path. For more clarity, I call some constants related to the HTTP/2 header from the http2.constants property. Let's create the server.js file.

const http2 = require('http2');
const { 
  HTTP2_HEADER_PATH, 
  HTTP2_HEADER_METHOD, 
  HTTP2_HEADER_CONTENT_TYPE,
  HTTP2_HEADER_CONTENT_LENGTH,
  HTTP2_HEADER_LAST_MODIFIED,
  HTTP2_HEADER_AUTHORITY,
  HTTP2_HEADER_STATUS,
  HTTP_STATUS_INTERNAL_SERVER_ERROR
} = http2.constants;

const mime = require('mime');
const path = require('path');
const fs = require('fs');
const fsp = require('fs/promises');
const { O_RDONLY } = fs.constants;

Currently, most browsers require TLS encrypted communication for HTTP/2 so that for this demo, we need to generate a self-signed certificate and include the certificate as the server parameter.

const serverPort = 3000;
const publicLocation = 'public'; // directory to store static files
const serverOptions = {
  key: fs.readFileSync('./your-selfsigned-key.pem'),
  cert: fs.readFileSync('./your-selfsigned-cert.pem')
}

We need to create a public directory. Then, create several static files including index.html, app.js, and style.css inside the directory. We can write any methods or declarations inside those files for demo purposes. The index.html file should include app.js and style.css on the head or body.

In server.js, we create a function that will handle file sending through the HTTP/2 stream. In Node.js, the stream is an instance of the http2.ServerHttp2Stream object.

function sendFile(stream, fileLocation) {
  let fileHandle;

  fsp.open(fileLocation, O_RDONLY)
    .then((fh) => {
      fileHandle = fh;
      return fileHandle.stat();
    })
    .then((stats) => {
      // setup file sending header
      const headers = {
        [HTTP2_HEADER_CONTENT_LENGTH]: stats.size,
        [HTTP2_HEADER_LAST_MODIFIED]: stats.mtime.toUTCString(),
        [HTTP2_HEADER_CONTENT_TYPE]: mime.getType(fileLocation)
      };

      // close the file in 'close' event of the stream
      stream.on('close', () => {
        fileHandle.close();
      });

      // send response with file descriptor
      stream.respondWithFD(fileHandle.fd, headers);
    })
    .catch((reason) => {
      stream.respond({
        [HTTP2_HEADER_STATUS]: HTTP_STATUS_INTERNAL_SERVER_ERROR
      });

      stream.end();
    });
}

Last, we define an HTTP/2 server object that will handle file requests. For this demo, the server only accepts any request to index.html file. Other requests will be responded with a plain text message.

const server = http2.createSecureServer(serverOptions);

server.on('stream', (stream, headers) => {

  // get some headers
  const method = headers[HTTP2_HEADER_METHOD].toLowerCase();
  const url = new URL(headers[HTTP2_HEADER_PATH], 'https://' + headers[HTTP2_HEADER_AUTHORITY]);
  const pathname = url.pathname.replace(/^\/+|\/+$/g, '');

  // handle root or index.html file request
  if (pathname==='' || pathname==='index.html') {
    if (stream.pushAllowed) {
      
      // push app.js
      stream.pushStream({
        [HTTP2_HEADER_PATH]: '/app.js'
      }, (err, pushStream) => {
        if (!err) {
          sendFile(pushStream, path.join(__dirname, publicLocation, 'app.js'));
        }
      });

      // push style.css
      stream.pushStream({
        [HTTP2_HEADER_PATH]: '/style.css'
      }, (err, pushStream) => {
        if (!err) {
          sendFile(pushStream, path.join(__dirname, publicLocation, 'style.css'));
        }
      });
    }

    // send index.html
    let indexFileLocation = path.join(__dirname, publicLocation, 'index.html');
    sendFile(stream, indexFileLocation);

  } else { // handle other requests
    stream.respond({
      'content-type': 'text/plain; charset=utf-8',
      ':status': 200
    });
    stream.end('hello world');
  }
});

server.listen(serverPort, () => {
  console.log('HTTP2 server listen to port ' + serverPort);
});

Now we can start the server and open the website in a browser with the address https://localhost:3000/index.html. If we open the browser inspection tool, we can see on the network panel that the initiator of app.js and style.css requests are called "Push". In other words, those files have already been cached by the browser, and the browser isn't required to make additional HTTP requests to the server.



Comments

Popular posts from this blog

Configuring Swap Memory on Ubuntu Using Ansible

If we maintain a Linux machine with a low memory capacity while we are required to run an application with high memory consumption, enabling swap memory is an option. Ansible can be utilized as a helper tool to automate the creation of swap memory. A swap file can be allocated in the available storage of the machine. The swap file then can be assigned as a swap memory. Firstly, we should prepare the inventory file. The following snippet is an example, you must provide your own configuration. [server] 192.168.1.2 [server:vars] ansible_user=root ansible_ssh_private_key_file=~/.ssh/id_rsa Secondly, we need to prepare the task file that contains not only the tasks but also some variables and connection information. For instance, we set /swapfile  as the name of our swap file. We also set the swap memory size to 2GB and the swappiness level to 60. - hosts: server become: true vars: swap_vars: size: 2G swappiness: 60 For simplicity, we only check the exi

Master Slave Replication to Automatically Backup Your MySQL Database

We can make backup for some databases by periodically running a kind of dump query, like mysqldump in MySQL. That's the simplest method but it can drain our server resources and it's not suitable for large databases. MySQL comes up with master-slave features that allow you to replicate your database to another location (slave). This mechanism enables MySQL to generate a log file which records any action performed to the database. Then, that action will be run in slave database too. For example, we have two database servers with IP address 192.168.0.1 (Master) and 192.168.0.2 (Slave). 1) Configure my.cnf in master server # Master Settings # locate where the changes record will be stored log-bin = /var/log/mysql/mysql-bin.log # set unique ID for master database in master-slave network (up to you) server-id = 111 innodb_flush_log_at_trx_commit = 1 sync_binlog = 1 # select database which will be replicated # by default system will log all databases binlog-do-db =

Installing VSCode Server Manually on Ubuntu

I've ever gotten stuck on updating the VSCode server on my remote server because of an unstable connection between my remote server and visualstudio.com that host the updated server source codes. The download and update process failed over and over so I couldn't remotely access my remote files through VSCode. The solution is by downloading the server source codes through a host with a stable connection which in my case I downloaded from a cloud VPS server. Then I transfer the downloaded source codes as a compressed file to my remote server through SCP. Once the file had been on my remote sever, I extracted them and align the configuration. The more detailed steps are as follows. First, we should get the commit ID of our current VSCode application by clicking on the About option on the Help menu. The commit ID is a hexadecimal number like  92da9481c0904c6adfe372c12da3b7748d74bdcb . Then we can download the compressed server source codes as a single file from the host.

Rangkaian Sensor Infrared dengan Photo Dioda

Keunggulan photodioda dibandingkan LDR adalah photodioda lebih tidak rentan terhadap noise karena hanya menerima sinar infrared, sedangkan LDR menerima seluruh cahaya yang ada termasuk infrared. Rangkaian yang akan kita gunakan adalah seperti gambar di bawah ini. Pada saat intensitas Infrared yang diterima Photodiode besar maka tahanan Photodiode menjadi kecil, sedangkan jika intensitas Infrared yang diterima Photodiode kecil maka tahanan yang dimiliki photodiode besar. Jika  tahanan photodiode kecil  maka tegangan  V- akan kecil . Misal tahanan photodiode mengecil menjadi 10kOhm. Maka dengan teorema pembagi tegangan: V- = Rrx/(Rrx + R2) x Vcc V- = 10 / (10+10) x Vcc V- = (1/2) x 5 Volt V- = 2.5 Volt Sedangkan jika  tahanan photodiode besar  maka tegangan  V- akan besar  (mendekati nilai Vcc). Misal tahanan photodiode menjadi 150kOhm. Maka dengan teorema pembagi tegangan: V- = Rrx/(Rrx + R2) x Vcc V- = 150 / (150+10) x Vcc V- = (150/160) x 5

Setting Up Next.js Project With ESLint, Typescript, and AirBnB Configuration

If we initiate a Next.js project using the  create-next-app tool, our project will be included with ESLint configuration that we can apply using yarn run lint . By default, the tool installs eslint-config-next and extends next/core-web-vitals in the ESLint configuration. The Next.js configuration has been integrated with linting rules for React and several other libraries and tools. yarn create next-app --typescript For additional configuration such as AirBnB, it is also possible. First, we need to install the peer dependencies of eslint-config-airbnb . We also add support for Typescript using eslint-config-airbnb-typescript . yarn add --dev eslint-config-airbnb eslint-plugin-import eslint-plugin-jsx-a11y eslint-plugin-react eslint-plugin-react-hooks yarn add --dev eslint-config-airbnb-typescript @typescript-eslint/eslint-plugin @typescript-eslint/parser After that, we can update the .eslintrc.json file for the new configuration. { "extends": [ "airb

Resize VirtualBox LVM Storage

VirtualBox is a free solution to host virtual machines on your computer. It provides configuration options for many components on our machine such as memory, storage, networking, etc. It also allows us to resize our machine storage after its operating system is installed. LVM is a volume manager in a Linux platform that helps us to allocate partitions in the system and configure the storage size that will be utilized for a specific volume group. There are some points to be noticed when we work with LVM on VirtualBox to resize our storage. These are some steps that need to be performed. 1. Stop your machine before resizing the storage. 2. Set new storage size using GUI by selecting " File > Virtual Media Manager > Properties " then find the desired virtual hard disk name that will be resized. OR , by running a CLI program located in " Program Files\Oracle\VirtualBox\VBoxManage.exe ".  cd "/c/Program Files/Oracle/VirtualBox" ./VBoxManage.exe list