෴ A node.js HTTP server in your browser ෴
Latest commit 34648c2 May 18, 2013 @jed 0.1.3
Failed to load latest commit information.
.gitignore Initial commit Aug 5, 2012
LICENSE.txt Create LICENSE.txt Mar 9, 2013
README.md fix broken link in readme Oct 11, 2012
browserver.js ensure fixed GUI length May 17, 2013
package.json 0.1.3 May 17, 2013


෴ browserver-client ෴

This is a browserver client, for the browser.

browserver-client exposes the important bits of the node.js http API in the browser, allowing it to receive incoming HTTP requests and make outgoing HTTP requests via WebSockets.

This library, along with browserver-node, is all the code you need to set up your own browserver.


In index.html:

<!doctype html>
    <title>My Browserver App</title>
    <script src="/optional/path/to/websocket-shim"></script>
    <script src="/path/to/browserver"></script>
    <script src="/app.js"></script>

In app.js:

// to handle incoming HTTP requests,
// use the standard node.js http.Server API
var server = http.createServer(function(req, res) {
  if (req.method != "GET") {
    res.writeHead(405, {"Content-Type": "text/plain"})
    return res.end("Method not allowed")

  var pathname = req.url.split("?")[0]

  if (pathname != "/hello") {
    res.writeHead(404, {"Content-Type": "text/plain"})
    return res.end("Not found.")

  res.writeHead(200, {"Content-Type": "text/plain"})
  res.end("Hello, world!")

// establish a WebSocket (or compatible) connection,
// in this case using engine.io
var ws = new eio.Socket({host: "myserver.com"})

// bind the browserver HTTP server to the WebSocket
// and wait for connections from the browserver proxy!

// to make outgoing HTTP requests w/o cross-domain issues,
// use http.get or http.request
http.get("http://www.google.com/index.html", function(res) {
  console.log("Google answered back!")


The browserver-client API is basically a port of the node.js http API, with a few caveats:

  • Streaming is not supported. This means a ServerRequest or ClientResponse will only emit one data event, and that multiple calls to the write method of a ServerResponse or ClientRequest will be buffered locally and sent when end is called. The data events are provided for compatibility, but aren't technically needed, since the body itself is stored on the body property of the ServerRequest or ClientResponse.

  • The aspects of the node.js implementation that don't map well to the browser (such as writeContinue and addTrailers methods, and client agents) have been omitted.

Otherwise, if there is a method or behavior that differs from what you'd expect on node.js, please file an issue.


  • Include more client tests in the phantomjs tests run for browserver-node
  • Make an exhaustive list of the HTTP APIs supported and not supported.
  • Consider enabling support for addEventListener events.