No description, website, or topics provided.
Clone or download
Pull request Compare This branch is 888 commits behind cloudfoundry:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.

Build Status


This repository contains the source code for a Go implementation of the Cloud Foundry router.

This router is now used on, replacing the old implementation.


The original router can be found at cloudfoundry/router. The original router is backed by nginx, that uses Lua code to connect to a Ruby server that -- based on the headers of a client's request -- will tell nginx which backend it should use. The main limitations in this architecture are that nginx does not support non-HTTP (e.g. traffic to services) and non-request/response type traffic (e.g. to support WebSockets), and that it requires a round trip to a Ruby server for every request.

The Go implementation of the Cloud Foundry router is an attempt in solving these limitations. First, with full control over every connection to the router, it can more easily support WebSockets, and other types of traffic (e.g. via HTTP CONNECT). Second, all logic is contained in a single process, removing unnecessary latency.

Getting started

The following instructions may help you get started with gorouter in a standalone environment.


You should have a GOPATH configured as described in

To install exactly the dependecies vendored with gorouter, use godep

go get -v
go get -v

cd $GOPATH/src/

godep restore ./...

Running Tests

We are using Gocheck, to run tests

scripts/test uses go test ./... internally. Any flags passed the scripts/test will be passed to go test ./...


# just run tests whose names match Registry
./scripts/test -gocheck.f=Registry

# run the tests for only the registry package
./scripts/test ./registry


# Start NATS server in daemon mode
go get
gnatsd &

# Start gorouter


When gorouter starts, it sends router.start. This message contains an interval that other components should then send router.register on. If they do not send a router.register for an amount of time considered "stale" by the router, the routes are pruned. The default "staleness" is 2 minutes.

The format of this message is as follows:

  "id": "some-router-id",
  "hosts": [""],
  "minimumRegisterIntervalInSeconds": 5

If a component comes online after the router, it must make a NATS request called router.greet in order to determine the interval. The response to this message will be the same format as router.start.

The format of route updates are as follows:

  "host": "",
  "port": 4567,
  "uris": [
  "tags": {
    "another_key": "another_value",
    "some_key": "some_value"

Such a message can be sent to both the router.register subject to register URIs, and to the router.unregister subject to unregister URIs, respectively.

$ nohup ruby -rsinatra -e 'get("/") { "Hello!" }' &
$ nats-pub 'router.register' '{"host":"","port":4567,"uris":["",""],"tags":{"another_key":"another_value","some_key":"some_value"}}'
Published [router.register] : '{"host":"","port":4567,"uris":["",""],"tags":{"another_key":"another_value","some_key":"some_value"}}'
$ curl


Gorouter provides /varz and /healthz http endpoints for monitoring.

The /routes endpoint returns the entire routing table as JSON. Each route has an associated array of host:port entries.

Aside from the two monitoring http endpoints (which are only reachable via the status port), specifying the User-Agent header with a value of HTTP-Monitor/1.1 also returns the current health of the router. This is particularly useful when performing healthchecks from a Load Balancer.

Because of the nature of the data present in /varz and /routes, they require http basic authentication credentials which can be acquired through NATS. The port, user and password (pass is the config attribute) can be explicitly set in the gorouter.yml config file's status section.

  port: 8080
  user: some_user
  pass: some_password

Example interaction with curl:

curl -vvv -A "HTTP-Monitor/1.1"
* About to connect() to port 80 (#0)
*   Trying connected
> GET / HTTP/1.1
> User-Agent: HTTP-Monitor/1.1
> Host:
> Accept: */*
< HTTP/1.1 200 OK
< Date: Mon, 10 Feb 2014 00:55:25 GMT
< Transfer-Encoding: chunked
* Connection #0 to host left intact
* Closing connection #0

curl -vvv "http://someuser:somepass@"
* About to connect() to port 8080 (#0)
*   Trying
* connected
* Connected to ( port 8080 (#0)
* Server auth using Basic with user 'someuser'
> GET /routes HTTP/1.1
> Authorization: Basic c29tZXVzZXI6c29tZXBhc3M=
> User-Agent: curl/7.24.0 (x86_64-apple-darwin12.0) libcurl/7.24.0 OpenSSL/0.9.8r zlib/1.2.5
> Host:
> Accept: */*
< HTTP/1.1 200 OK
< Content-Type: application/json
< Date: Mon, 25 Mar 2013 20:31:27 GMT
< Transfer-Encoding: chunked


The router's logging is specified in its YAML configuration file, in a steno configuration format. The meanings of the router's log levels are as follows:

  • fatal - An error has occurred that makes the current request unservicable. Examples: the router can't bind to its TCP port, a CF component has published invalid data to the router.
  • warn - An unexpected state has occurred. Examples: the router tried to publish data that could not be encoded as JSON
  • info, debug - An expected event has occurred. Examples: a new CF component was registered with the router, the router has begun to prune routes for stale droplets.


Please read the contributors' guide