Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Simple HTTP for browser
JavaScript CoffeeScript HTML
tag: 1.8.0

Fetching latest commit…

Cannot retrieve the latest commit at this time

Failed to load latest commit information.


Some simple classes for working with http in browser (for example with simq).

Now it is really simple and more functions will be added.

http-browser uses q promise pattern and is instance of EventEmitter.


$ npm install browser-http


var http = require('browser-http');

http.request('', {type: 'GET'}).then(function(response) {
}, function(e) {
    throw e;        // some error occurred

In then function, you will get response object with data from server.


var http = require('browser-http');



In every http function, you can set other options. Now it is just type and data.

  • type: GET, POST, PUT or DELETE
  • data: literal object of data which needs to be send to server

Response object

Basically it is just wrapper for some data from XMLHttpRequest.

  • state
  • status
  • statusText
  • rawData: same like responseText
  • data: same like responseText or literal object (json)
  • xml: same like responseXML


If content-type in response header is application/json then your data will be automatically transformed into js object.

If you can not set this header on your server, than you can use *Json methods.

http.getJson('').then(function(response) {
    console.log(;     // output will be object


Requests queue

By default all your requests are called from queue one by one, so there is always just one request running (or zero). Inspiration from this article

You can of course disable this behavior:

http.useQueue = false;


It is very easy to work with jsonp requests.

http.jsonp('').then(function(response) {


You can listen for all http events with your own functions.

http.on('send', function(response, request) {
    console.log('In any moment, new http request will be send to server');

http.on('complete', function(response, request) {
    console.log('I just finished some request, but there may be some errors');

http.on('success', function(response, request) {
    console.log('I have got response from server without any error :-)');

http.on('error', function(err, response, request) {
    console.log('Sorry, there was some error with this response');


Sometimes it will be better to register whole group of events and this group is called extension.

http.addExtension('nameOfMyExtension', {
    send: function(response, request) {},
    complete: function(response, request) {},
    success: function(response, request) {},
    error: function(err, response, request) {},

You can also remove other extensions.


Build in extensions

browser-http already comes with few extensions. Originally they were created for project build on Nette framework, but can be used on any other project.

Loading cursor

new (require('browser-http/Extensions/Loading'));

Every time new request is send, your cursor is changed into progress cursor. After receiving response from server, cursor is changed into auto.


new (require('browser-http/Extensions/Redirect'));

If your server sends json data with redirect variable, then you will be redirected to address in this variable.


new (require('browser-http/Extensions/Snippets'));

If in response data is snippets object with html id and content pairs, then browser-http will iterate throw this object, find element in page with given id and change content of this element into the one from given data.

This extension depends on jquery.

Ajax links

new (require('browser-http/Extensions/Links'));

This is not true extension for browser-http. It listen for all click events on a links with class ajax but not with class not-ajax and after this click, it creates ajax request.

Depends on jquery.

Ajax forms

This is the same like the previous one, but apply for all forms with ajax class. This extension can not handle forms with file uploads. Depends on jquery.


$ cd test
$ node data.js

in another terminal:

$ npm test


  • 1.8.0

    • Requests are added into queue
    • Added support for jsonp
  • 1.7.1

    • Added some tests
    • Bug with responses without content-type header
  • 1.7.0

    • Refactoring
    • buildQuery and urlencode moved to browser-http/Helpers
    • Instance of EventEmitter
  • 1.6.4

    • Optimizations + bug with sending data
  • 1.6.3

    • Bug with buildQuery - replaced with the real one from jQuery
  • 1.6.2

    • Just removed some useless code
  • 1.6.1

    • Forgot to add Extensions/Links shortcut
  • 1.6.0

    • buildQuery should got the same output like jQuery.param
    • Added some extensions
  • 1.5.2

    • Bug with sending data via POST method
  • 1.5.1

    • Bug with X-Requested-With header
  • 1.5.0

    • Added method isHistoryApiSupported
  • 1.4.0

    • Sending X-Requested-With header
  • 1.3.1 - 1.3.5

    • Bugs
  • 1.3.0

    • Added urlencode and buildQuery methods
    • Prepared changelog
    • Added some tests
    • Some bugs and optimizations
    • Transforming response data into json if mime type is application/json
Something went wrong with that request. Please try again.