Use an `Authorization` header instead, which is a safer choice than URL embedded identities (aka `http://user:pass@example.com`). [Chrome 19 dropped support][chromium128323] for URL embedded identities in XMLHttpRequest for security reasons.

Added documentation note about how this will overwrite any existing `Authorization` header that the user may have set.

[chromium128323]: https://code.google.com/p/chromium/issues/detail?id=128323

XDomainRequest support

Conflicts:
	package.json

Conflicts:
	lib/adapters/xhr.js

Adding transparent decompression if `content-encoding` is set

follow redirects

add test case for `transparent decompression` for `content-encoding` being set in the response headers

Don't call slice on arguments

Don't use utils.forEach to loop over arguments

Update README.md: instantiation