Merge branch 'release/v0.4.1' into develop
Upgrade BK middleware to Faraday 0.8. cr:jasonp

- Upgraded gemspec to use Faraday 0.8
- env.url is now vanialla URI and not Addressable::URI. Some hash manipulation foo.
- Releasing as 5.0.rc
- Updated specs.
- Log entry in CHANGELOG.
Enable SimpleCov coverage with rcov formatter

Triggered by an environment variable set by the rake task.
Merge pull request #8 from BlueKai/feature/coverage

Enable SimpleCov coverage with rcov formatter

cr: @Nymbil
Fix array variable handling

Needed to use array parameters with certain APIs.
Add spec for array variables

I ran this spec in the bare `support/0.4.x` branch and it fails there.
It passes here.
Bump version number; update CHANGELOG
Merge pull request #9 from BlueKai/handle_array_variables

Fix array variable handling

cr: @krobi64
Switch to new standard .gitignore file

Please use the global .gitignore file (at `~/.gitignore`) to ignore OS-
or tool-specific files.
Begin using Appraisal

Appraisal is a gem that lets us specify additional constraints for gem
development in order to test against multiple versions of dependencies.

We'll want to test this gem against Faraday 0.7 and 0.8, so I started
with those.
Partially revert 97437cb0

The rewritten test from 97437cb0 only passed with Faraday 0.8, so the
added complexity of the shared examples wasn't worth it. Fixing with
Appraisal.
Rewrite spec for both supported Faraday versions

Discovered Faraday itself has a build_url method which keeps us from
having to reference Addressable in a spec.
Merge pull request #10 from BlueKai/feature/multi_version_testing

Add appraisal; test on multiple Faraday versions

cr: @krobi64
Add back support for Array parameters

Took a while to get this right. Unfortunately, Faraday 0.7 and 0.8 can
never be totally compatible. Passing a params hash like `{a: [1, 2]}`
will result in a query string of "a=1&a=2" in Faraday 0.7 but produces
"a[]=1&a[]=2" in Faraday 0.8. We sign both cases correctly, but certain
Java APIs may not accept both forms.

Faraday 0.9 allows for pluggable URI generation but isn't done yet.
Merge pull request #11 from BlueKai/feature/nested_params_support

Add back support for Array parameters

cr: @krobi64
Merge tag 'v0.4.2' into develop

This merge doesn't really have any textual changes. Just wanted to
semantically tie develop back into the v0.4.2 change to add array
parameter support and get the CHANGELOG comment for that tag into
develop/master.

Conflicts:
	CHANGELOG.md
	lib/bluekai_middleware/authenticate.rb
	lib/bluekai_middleware/version.rb
	spec/lib/bluekai_middleware/authenticate_spec.rb
Switch to .ruby-version, require 1.9.3

Had to fix an initializer, but that was about all.

cr: nobody
Bump version for release candidate
Change encoding to use `%20` for spaces

A couple of bugs have cropped up recently in which queries with spaces
in arguments would receive a `403` status from services when they were
otherwise well-formed requests.

It appears the Java services have changed from expecting spaces encoded
as `+` to expecting `%20`. At first I thought this must be a long-lived
bug in the `Authenticate` class, but when I checked I noticed we have
_always_ sent spaces as `+` going back to May 2012. Indeed the specs
themselves tested for this case.
Merge handle_spaces_properly into release/0.5.0