Introduction to the NGINX JavaScript Module

Harnessing the Power and Convenience of JavaScript for Each Request

Editor – This is the first in a series of blog posts about the NGINX JavaScript module, which was formerly called nginScript (this post uses the names interchangeably). This post discusses why NGINX, Inc. developed its own implementation of JavaScript, and presents a sample use case. Check out the other posts to explore additional use cases:

• Introduction to the NGINX JavaScript Module
• Using the NGINX JavaScript Module to Progressively Transition Clients to a New Server
• Advanced Logging with the NGINX JavaScript Module in "Scaling MySQL with TCP Load Balancing and Galera Cluster"
• Data Masking for User Privacy with the NGINX JavaScript Module
• Load Balancing MQTT with the NGINX JavaScript Module for Session Persistence in "NGINX Plus for the IoT: Load Balancing MQTT"
• Using Client Certificates to Authenticate MQTT Clients in "NGINX Plus for the IoT: Encrypting and Authenticating MQTT Traffic"

We are pleased to announce that the NGINX JavaScript module is generally available as a stable module for NGINX and NGINX Plus (in NGINX 1.11.10 and later, and NGINX Plus R12 and later). [The module was formerly called nginScript; this post uses the names interchangeably.] We have been working steadily on nginScript since its launch in September 2015, adding the features and language support included in the stable module.

nginScript is a unique JavaScript implementation for NGINX and NGINX Plus, designed specifically for server‑side use cases and per‑request processing. It extends NGINX configuration syntax with JavaScript code in order to implement sophisticated configuration solutions.

The use cases are extensive, especially as nginScript is available for both HTTP and TCP/UDP protocols. Example use cases for nginScript include:

• Generating custom log formats with values not available from regular NGINX variables
• Implementing new load‑balancing algorithms
• Parsing TCP/UDP protocols for application‑level sticky sessions

There are of course many more possibilities for nginScript, and more still that have yet to be implemented. Although we are pleased to announce general availability of nginScript and be able to recommend it for production use, there is a roadmap of planned improvements that will enable yet more use cases, such as:

• Inspecting and modifying the body of HTTP requests and responses (already supported for TCP/UDP traffic)
• Making HTTP subrequests from nginScript code
• Writing authentication handlers for HTTP requests (already supported for TCP/UDP traffic)
• Reading and writing files

Before discussing nginScript in more detail, let’s first address two common misconceptions.

The NGINX JavaScript Module Is Not Lua

The NGINX community has created several programmatic extensions over the years. At the time of writing, Lua is the most popular of these; it’s available as a module for NGINX and a certified third‑party module for NGINX Plus. The Lua module and add‑on libraries provide deep integration with the NGINX core and a rich set of functionality, including a driver for Redis.

Lua is a powerful scripting language. It, however, remains fairly niche in terms of adoption and is not typically found in the “skillset toolbox” of the frontend developer or DevOps engineer.

nginScript does not seek to replace Lua and it will be some time before nginScript has a comparable level of functionality. The goal of nginScript is to provide programmatic configuration solutions to the widest possible community by using a popular programming language.

The NGINX JavaScript Module Is Not Node.js

nginScript does not aim to turn NGINX or NGINX Plus into an application server. In simple terms, the use cases for nginScript are akin to middleware, as the code execution happens between the client and the content. Technically speaking, while Node.js shares two things with the combination of nginScript and NGINX or NGINX Plus – an event‑driven architecture and the JavaScript programming language – the similarities end there.

Node.js uses the Google V8 JavaScript engine, whereas nginScript is a bespoke implementation of the ECMAScript standards, designed specifically for NGINX and NGINX Plus. Node.js has a persistent JavaScript virtual machine in memory and performs routine garbage collection for memory management, whereas nginScript initializes a new JavaScript virtual machine and the necessary memory for each request and frees the memory when the request is completed.

JavaScript as a Server-Side Language

As mentioned above, nginScript is a bespoke implementation of the JavaScript language. All other existing JavaScript runtime engines are designed to be executed within a web browser. The nature of client‑side code execution is different from server‑side code execution in many ways – from the availability of system resources to the possible number of concurrent runtimes.

We decided to implement our own JavaScript runtime in order to meet the requirements of server‑side code execution and fit elegantly with NGINX’s request‑processing architecture. Our design principles for nginScript are these:

• Runtime environment lives and dies with the request

  nginScript uses single‑threaded bytecode execution, designed for quick initialization and disposal. The runtime environment is initialized per request. Startup is extremely quick, because there is no complex state or helpers to initialize. Memory is accumulated in pools during execution and released at completion by freeing the pools. This memory management scheme eliminates the need to track and free individual objects or to use a garbage collector.

• Non‑blocking code execution

  NGINX and NGINX Plus’ event‑driven model schedules the execution of individual nginScript runtime environments. When an nginScript rule performs a blocking operation (such as reading network data or issuing an external subrequest), NGINX and NGINX Plus transparently suspend execution of that VM and reschedule it when the event completes. This means that you can write rules in a simple, linear fashion and NGINX and NGINX Plus schedule them without internal blocking.

• Implement only the language support that we need

  The specifications for JavaScript are defined by the ECMAScript standards. nginScript follows ECMAScript 5.1 with some ECMAScript 6 for mathematical functions. Implementing our own JavaScript runtime gives us the freedom to prioritize language support for server‑side use cases and ignore what we don’t need. We maintain a list of supported and not‑yet‑supported language elements.

• Close integration with request‑processing phases

  NGINX and NGINX Plus process requests in distinct phases. Configuration directives typically operate at a specific phase and native NGINX modules often take advantage of the ability to inspect or modify a request at a particular phase. nginScript exposes some of the processing phases through configuration directives to give control over when the JavaScript code is executed. This integration with the configuration syntax promises the power and flexibility of native NGINX modules with the simplicity of JavaScript code.

  The table below indicates which processing phases are accessible via nginScript at the time of writing, and the configuration directives that provide it.

  Processing Phase	HTTP Module	Stream Module
  Access – Network connection access control	❌	✅ js_access
  Pre-read – Read/write body	❌	✅ js_preread
  Filter – Read/write body during proxy	❌	✅ js_filter
  Content – Send response to client	✅ js_content	❌
  Log / Variables – Evaluated on demand	✅ js_set	✅ js_set

Getting Started with the NGINX JavaScript Module – A Real‑World Example

nginScript is implemented as a module that you can compile into an open source NGINX binary or dynamically load into NGINX or NGINX Plus. Instructions for enabling nginScript with NGINX and NGINX Plus appear at the end of this article.

In this example we use NGINX or NGINX Plus as a simple reverse proxy and use nginScript to construct access log entries in a specialized format, that:

• Includes the request headers sent by the client
• Includes the response headers returned by the backend
• Uses key‑value pairs for efficient ingestion into and searching with log processing tools such as the ELK Stack (now called Elastic Stack), Graylog, and Splunk

The NGINX configuration for this example is extremely simple.

As you can see, the nginScript code does not sit inline with the configuration syntax. We use the js_include directive to specify the file that contains all of our JavaScript code. The js_set directive defines a new NGINX variable, $access_log_with_headers, and the JavaScript function that populates it. The log_format directive defines a new format called kvpairs which writes each log line with the value of $access_log_with_headers.

The server block defines a simple HTTP reverse proxy that forwards all requests to http://www.example.com. The access_log directive specifies that all requests will be logged with the kvpairs format.

Let’s now look at the JavaScript code that prepares the log line. We have two functions:

• kvHeaders – A support function that converts the headers object to a string of key‑value pairs. Support functions must be declared before the function that calls them.
• kvAccessLog – The function defined in the js_set directive within the NGINX configuration. It receives two object arguments that represent the client request (req) and the backend server’s response (res). Built‑in objects like these can be passed to all HTTP nginScript functions.

As can be seen in the kvAccessLog function, it is the return value that is passed to the js_set configuration directive. Bear in mind that NGINX variables are evaluated on demand and this in turn means that the JavaScript function defined by js_set is executed when the value of the variable is required. In this example, $access_log_with_headers is used in the log_format directive and so kvAccessLog() is executed at log time. Variables used as part of map or rewrite directives trigger the corresponding JavaScript execution at an earlier processing phase.

We can see this nginScript‑enhanced logging solution in action by passing a request through our reverse proxy and observing the resulting log file entry.

$ curl http://127.0.0.1/
$ tail --lines=1 /var/log/nginx/access_headers.log
2017-03-14T14:36:53+00:00 client=127.0.0.1 method=GET uri=/ status=200 req.Host=127.0.0.1 req.User-Agent=curl/7.47.0 req.Accept=*/* res.Cache-Control=max-age=604800 res.Etag=\x22359670651+ident\x22 res.Expires='Tue, 21 Mar 2017 14:36:53 GMT' res.Last-Modified='Fri, 09 Aug 2013 23:54:35 GMT' res.Vary=Accept-Encoding res.X-Cache=HIT

Much of the utility of nginScript is a result of its access to NGINX internals. This example utilizes several properties of the request and response objects. The Stream nginScript module for TCP and UDP applications utilizes a single session object with its own set of properties. See our blog for other examples of nginScript solutions:

• HTTP – Using nginScript to progressively transition clients to a new server
• Stream – Logging the SQL method when load balancing Galera Cluster

We’d love to hear about the use cases that you come up with for nginScript – please tell us about them in the comments section below.

---

Enabling the NGINX JavaScript Module for NGINX and NGINX Plus

[Editor – The NGINX JavaScript module was formerly called nginScript.]

• Loading the NGINX JavaScript Module for NGINX Plus
• Loading the NGINX JavaScript Module for Open Source NGINX
• Compiling the NGINX JavaScript Module as a Dynamic Module for Open Source NGINX

Loading the NGINX JavaScript Module for NGINX Plus

The NGINX JavaScript module is available as a free dynamic module for NGINX Plus subscribers (for open source NGINX, see Loading the NGINX JavaScript Module for Open Source NGINX below).

1. Obtain the module itself by installing it from the NGINX Plus repository.

   • For Ubuntu and Debian systems:

     $ sudo apt‑get install nginx-plus-module-njs

   • For RedHat, CentOS, and Oracle Linux systems:

     $ sudo yum install nginx-plus-module-njs

2. Enable the module by including a load_module directive for it in the top‑level ("main") context of the nginx.conf configuration file (not in the http or stream context). This example loads the the NGINX JavaScript modules for both HTTP and TCP/UDP traffic.

   load_module modules/ngx_http_js_module.so;
   load_module modules/ngx_stream_js_module.so;

3. Reload NGINX Plus to load the the NGINX JavaScript modules into the running instance.

   $ sudo nginx -s reload

Loading the NGINX JavaScript Module for Open Source NGINX

If your system is configured to use the official prebuilt packages for open source NGINX and your installed version is 1.9.11 or later, then you can install the NGINX JavaScript module as a prebuilt package for your platform.

1. Install the prebuilt package.

   • For Ubuntu and Debian systems:

     $ sudo apt-get install nginx-module-njs

   • For RedHat, CentOS, and Oracle Linux systems:

     $ sudo yum install nginx-module-njs

2. Enable the module by including a load_module directive for it in the top‑level ("main") context of the nginx.conf configuration file (not in the http or stream context). This example loads the the NGINX JavaScript modules for both HTTP and TCP/UDP traffic.

   load_module modules/ngx_http_js_module.so;
   load_module modules/ngx_stream_js_module.so;

3. Reload NGINX Plus to load the the NGINX JavaScript modules into the running instance.

   $ sudo nginx -s reload

Compiling NGINX JavaScript as a Dynamic Module for Open Source NGINX

If you prefer to compile an NGINX module from source:

1. Follow these instructions to build either or both the HTTP and TCP/UDP NGINX JavaScript modules from the open source repository.
2. Copy the module binaries (ngx_http_js_module.so, ngx_stream_js_module.so) to the modules subdirectory of the NGINX root (usually /etc/nginx/modules).
3. Perform Steps 2 and 3 in Loading the NGINX JavaScript Module for Open Source NGINX.