HTTP Simple Proxy

===============

• About
• Installation and basic usage
• Features
  • Proxy
  • URL rewrite
  • Redirect
  • SSL
  • Logging
  • HTTP authentication
  • Add header
  • Compression / GZIP
  • Regexp matching
  • Error handling
  • Serve static directory
  • Advanced routing
• Class HttpSimpleProxy
• Credits
• License

About

http-simple-proxy exists so you can run multiple applications on the same port

This is a rewrite work of http-master to make it simpler, if you need a more robust approach use http-master

It is a front end http service with with easy setup of reverse proxy/redirecting/other-actions logic.
It means it was designed to run on your port 80 and 443 but can run on any.

http-simple-proxy allows you to easily define rules which domain should target which server and if no rules match, everything else could go to the Apache server.

This way you setup your SSL in one place, in http-simple-proxy and even non-SSL compatible http server can be provided with HTTPS. Many different flexible routing configurations are possible to set up.

Some of the features:

• Same HTTPS configuration of https module
• Supports web sockets.
• Easy all in one place configuration for every listening port (eg. 80 and 443 together)
  • Setup reverse proxy with optional URL rewriting and optional regexp matching of host and path.
  • Setup redirect with optional regexp matching to construct final URL.
  • Setup basic static files server for a given route.
  • Setup Basic-AUTH for a given route (sponsored feature)
  • Create logs in apache format for any given point in routing setup.
  • Easily turn any local or remote TCP servers to web sockets. (websockify) Destination may be determined dynamically from a path.
  • Allows flexible definition of matching behaviour.
  • Enable compression on one, any or all of the routes.
  • Add headers to any defined route.

Installation and basic usage

npm install --save http-simple-proxy

var HttpSimpleProxy = require('http-simple-proxy');
var httpSimpleProxy = new HttpSimpleProxy();
httpSimpleProxy.init({
 ports: {
  80: {
    router: {
      // two rules to forward 2 domains to ports
      "domain1.com": 3333,
      "www.domain1.com": 3334,
    },
  },
 }
}, function(err) {
  if(err)
    console.error('Proxy error:', err)
 // listening
 console.info('http-simple-proxy started')
});

Proxy

Proxy is a default action what to do with a http request but in each place where a number or host are used, you could do a redirect as well.

Proxy all requests from port 80 to port 4080

# Short-hand syntax
ports: {
  80: 443
}

# A bit longer short-hand syntax (but could be used with ssl)
ports: {
  443: {
    router: 4080,
    ssl: {} # this needs setting up
  }
}

# Normal syntax - baseline for extending
ports: {
  80: {
    router: {
      "*": 4080
    }
  }
}

Proxy by domain name

ports: {
  80: {
    router: {
      // two rules will match all domain1.com and www.domain1.com requsts
      "domain1.com": 3333,
      "www.domain1.com": 3334,
      // will match all domain2.com requsts (but not www.domain2.com)
      // and proxy it to a host with different ip in internal network
      "domain2.com": "192.168.1.1:80",
      // this will match every subdomain of domain4.com, but not domain4.com
      "*.domain4.com" : "5050",
      // this will match every subdomain of domain4.com, and domain4.com
      "*?.domain4.com": "some_machine_by_host:4020"
    }
  }
}

Proxy by domain name and/or path

ports: {
  80: {
    router: {
      // will match domain1.com/path1 or domain1/path/whatever or domain1/path/whatever/whatever
      // Last * in path match matches everything and makes last slash optional
      "domain1.com/path1/*" : 5010,
      "domain1.com/path2/*" : 5011,
      // and rest goes to 5012 - this needs to be defined as patch matching
      // happens after domain matching
      "domain1.com/*" : 5012
    }
  }
}

Proxy port settings

ports: {
  80: {
    router: {
      "domain.com" : 5012
    },
    agentSettings: {
      keepAlive: true
    },
    proxyTargetTimeout: 1500,
    proxyTimeout: 1000
  }
}

In addition to router, following setting could be set per port:

• agentSettings, for full list of options check node documentation for http.Agent. You can also set default agent settings at the root level in your config, using the same agentSettings name
• proxyTargetTimeout sets timeout for target connection
• proxyTimeout sets timeout for proxy connection

URL rewrite

All proxy example can be adapted to also do URL rewriting. All matching rules can do either wildcard (implicit) regexp matching explicit regexp matching. Let's focus on implicit first.

ports: {
  80: {
    router: {
      // * will match all subdomains
      // http://abc.domain.com will rewrite to -> /abc/
      // http://abc.domain.com/test will rewrite to -> /abc/test
      // http://xyz.abc.domain.com/test will rewrite to -> /xyz.abc/test
      "*.domain.com": "5050/[1]/[path]"
    }
  }
}

So what if you want to rewrite two levels of subdomains?

ports: {
  80: {
    router: {
      "*.*.domain.com" : "5050/[1]/[2]/[path]"
    }
  }
}

You can also match paths and rewrite:

ports: {
  80: {
    router: {
      "*.localhost/test/*": "[1].somewhere.net/something/[2]"
    }
  }
}

Everything above and more you can also do with regexp matching which is described in Regexp matching section.

Redirect

Redirect is a feature implemented and invoked in a similiar way to proxy. The different is that instead of proxy target, you should point rules to "redirect -> http://target". The way target is constructed often is desired to be dynamic, for example that's how https to http redirect is usually used.

ports: {
  80: {
    router: {
      // rewrite all http://myapp.eu/* requests to https://myapp/eu/*
      // [path] is a special macro that will be replaced with the request's pathname
      "myapp.eu": "https://myapp.eu/[path]",
      // for example proxy rest to apache's port
      '*' : 80443
    }
  },
  443: {
    router: {
      // proxy to actual application
      "myapp.eu": 3333,
      // proxy rest to apache
      "*": 8080
    },
    ssl: {} # ssl should be configured here
  }
}

SSL

SSL can be configured for any port by simply providing "ssl" key to its entry, for example:

ports: {
  443: {
    router: {}, # your rules here
    ssl: {
      key: "/path/to/key/domain.key",
      cert: "/path/to/key/domain.crt",
      ca: "/path/to/ca/bundle/ca.pem",
      // alternatively above could be written as
      // ca: ["/path/to/ca1.crt", "/path/to/ca2.crt"]
      SNI: {
        "*.myapp.co.uk" : {
          key: "/path/to/key/myapp.key",
          cert: "/path/to/key/myapp.crt",
          ca: "/path/to/ca/bundle.pem"
        },
        "singledomain.net" : {
          key: "/path/to/key/singledomain.key",
          cert: "/path/to/key/singledomain.crt",
          ca: "/path/to/ca/bundle.pem"
        }
      }
    }
  }
}

Logging

To enable application log:

ports: {}, # your port config here
modules: {
  appLog: "/path/to/app.log", //file log
  consoleLog: true, //console
}

To enable general access log:

middleware: ["log -> /path/to/access.log"],
ports: {} # your port config here

To enable logging per route (note, consult Advanced routing for more details)

ports: {
  80: {
    router: {
      "myapp.net": ["log -> /path/to/myapp.log", 3333]
    }
  }
}

Rule of thumb is, wherever you had some target be it proxy or redirect, you can turn it to an array and place logging rule as first element.

Logging is in apache format.

Note: you may log to the same file from multiple routes, not a problem.

HTTP authentication

ports: {
  80: {
    router: {
      "myapp.net": ["auth -> file.passwd", 3333]
    }
  }
}

Basically you need to generate a passwd file and point http-simple-proxy to it. You can generate one with [node version of htpasswd]{https://www.npmjs.org/package/htpasswd}.

Add header

You can add one or more arbitrary requests to incoming headers/

ports: {
  80: {
    router: {
      "myapp.net": ["addHeader -> X-Some-Header1=Value1", "addHeader -> X-Some-Header2=Value2", 3333]
    }
  }
}

GZIP Compression

The single passed argument is compression level, from 1 to 9. 9 is most compression but slowest. To enable compression for all requests:

middleware: ["gzip -> 9"],
ports: {
  router: {} #your rules here
}

To enable compression for a single route:

ports: {
  router: {
    "domain.com" : ["gzip -> 9", 3333]
  }
}

Regexp matching

Short-hand matching format with using * or *? can be replaced by using explicit regexp expression, such as this:

ports: {
  80: {
    # [1] will contain app1 or app2, each number will reference regexp catch groups
    "^(app1|app2)\\.go\\.there\\.com": "5050/[1]"
  }
}

Only problem is the necessity to escape characters for string inclusion. Named groups are also supported. Please open an issue to request more docs.

Error handling

HTTP master will report some errors in plain text, you can override this behaviour by providing a custom html error page:

ports: {}, # your port config here
errorHtmlFile: "/path/to/error.html"

The html file may reference simple images which will be embedded to the response in form of base64. It cannot reference other files. Error html needs to be fast.

You can in fact trigger errors manually as well, for scheduled downtime for example:

ports: {
  80: {
    # this will report error 503
    "domain.com" : "reject -> 503"
  }
}

Serve static directory

You may also serve a static files , example:

ports: {
  80: {
    "/assets" : "static -> /home/domain/assets",
    "domain.com/*" : "static -> /home/domain/[1]",
  }
}

Please open an issue to request more docs.

Advanced routing

Advanced routing refers to ability of nesting multiple layers of rules, such as:

ports: {
  80 : {
    "*.domain.com" : ["log -> domain.log", {
      "*/path1" : 3333,
      "*/path2" : 3334,
      "*/*": 3335
    }]
  }
}

Please open an issue to request more docs.

Class HttpSimpleProxy

Event: 'allWorkersStarted'

function() Emitted after succesful .init()

Event: 'allWorkersReloaded'

function() Emitted after succesful .reload()

Event: 'logNotice'

function(msg) Helpful logging information in case something got wrong.

Event: 'logError'

function(msg) Information about errors that could be logged.

Event: 'error'

function(err) Emitted on failure to listen on any sockets/routes or failure to use given configuration.

httpSimpleProxy.init(config, [callback])

Initialize http master with a given config. See the section about config to learn about acceptable input. Callback if given will call function(err). This function should be called only once.

httpSimpleProxy.reload(config, [callback])

Perform a zero-downtime reload of configuration. Should be very fast and ports will not stop listening. Stopping httpSimpleProxy may be done using httpSimpleProxy.reload({}). Which should close all servers.

Credits

Rewrite work of http-master

Thanks to

• Damian Kaczmarek [e-mail]
• Damian Nowak [e-mail]
• Sergey Zarouski [e-mail]

License

Licensed under the MIT license, see LICENSE for details.