Capturing Traffic from Node.js Libraries


Product Version 1.0.0 and above
Node.js Module http
Node.js Module request


Many developers use Fiddler Everywhere to capture traffic from Node.js libraries that make HTTP and HTTPS requests. How can I proxy these requests so that I can capture and analyze them with Fiddler Everywhere?


Some Node.js modules, such as request, are reading the proxy information from the Windows environment variable (global proxy settings). Others like the state HTTP module do not respect the global proxy configuration of Node.js and you need to proxy their requests explicitly.

This section demonstrates the basic approach for each of the mentioned scenarios.

Setting the Proxy Globally

This scenario is useful for libraries like request that reuse the proxy settings in the environment variables. With Node.js, you can set the proxy directly in the terminal.

set https_proxy=
set http_proxy=

Once the above settings are applied, you can now call modules like request and make the HTTP request. The request will be captured by Fiddler Everywhere. Once the capturing is over, you can revert the global proxy settings as follows:

set https_proxy=
set http_proxy=

Alternatively, instead of using the terminal, you can use simple JavaScript to set the environment variable through code.

The following example demonstrates the fiddler-everywhere-test.js file.

const url = require("url");
const fiddlerProxy = {
    protocol: "http:",
    hostname: "",
    port: 8866,
const setFiddlerProxy = () => {
    var proxyUrl = url.format(fiddlerProxy);
    env.http_proxy = proxyUrl;
    env.https_proxy = proxyUrl;
    // Use this only for debugging purposes as it introduces a security issue
const removeFiddlerProxy = () => {
    env.http_proxy = "";
    env.https_proxy = "";


// Make requests with libraries that reuse the global proxy settings.


Setting the Proxy Explicitly

The global proxy settings won't work for modules like the HTTP module where you need to proxy each HTTP request to Fiddler Everywhere. One way to solve that is to set the proxy through the code explicitly.

The following example demonstrates the fiddler-everywhere-test.js file.

"use strict";

const url = require("url");
const http = require("http");

const fiddlerEverywhereProxy = {
    protocol: "http:",
    hostname: "",
    port: 8866,

// Use this only for debugging purposes as it introduces a security issue.

const setFiddlerProxy = (options) => {
    if (typeof options === "string") { // Options can be URL string.
        options = url.parse(options);
    if (! && !options.hostname) {
        throw new Error("host or hostname must have value.");
    options.path = url.format(options);
    options.headers = options.headers || {};
    options.headers.Host = || url.format({
        hostname: options.hostname,
        port: options.port
    options.protocol = fiddlerEverywhereProxy.protocol;
    options.hostname = fiddlerEverywhereProxy.hostname;
    options.port = fiddlerEverywhereProxy.port;
    options.href = null; = null;
    return options;

const exampleUrl = "";
http.request(setFiddlerProxy(exampleUrl), (res) => {
}).end(); // Through Fiddler.

With the above, you can test the request through the terminal.

node fiddler-everywhere-test.js

As a result, Fiddler Everywhere will capture the request and the response.

Successfully captured NodeJS traffic

Setting Fiddler Everywhere alongside the Node Proxy

After setting the proxy, either globally or explicitly, for your Node.js process, Fiddler Everywhere will immediately start capturing all of the traffic that goes through the Node proxy. You can turn off the Live Traffic switch to capture only the process from your Node.js libraries. Turning on the Live Traffic switch will set Fiddler as a system proxy and the Live Traffic will start capturing traffic for all applications that use the OS system proxy.