Hi guys!

I think, that this method works incorrect.

In our project we have REST and the server returns a response in json format. One day, the server has changed a key. But at the same time continued to pass the tests and the error was discovered only accidentally discovered.

I think we should be checking for the key, there may be a key is more important than the match value.

As for checking the value. If we check the existence of a key, and the value should be checked on the key.

I look forward to your opinions.

Regards,
Dmitry.
Fixes double authorization headers

When using different HTTP basic credentials for separate requests, previous authentication headers are not cleared before adding the new ones.  As a consequence the request never gets authorized.

Signed-off-by: James Cauwelier <james.cauwelier@gmail.com>
two minor mispelling in README.md
Repaired getting of token
Change from path based comparison to URI based comparison
rename variable
Checking if token is array
Merge pull request #30 from nenadalm/master

Repaired getting of token
Update SymfonyDoctrineContext

SymfonyDoctrineContext now able to manage with few doctrine entity managers at once.
Merge pull request #35 from Exelenz/master

Improved SymfonyDoctrineContext
Update README.md

Added example: how to use SymfonyDoctrineContext to rebuild database schema
Merge pull request #36 from Exelenz/master

Docs improved
Merge pull request #31 from sizuhiko/ChangeUriBasedComparison

Change uri based comparison
Merge pull request #28 from bartoszrychlicki/master

Just minor misspelling in README file
Merge pull request #27 from jamescauwelier/fix-double-auth-headers

Fixes double authorization headers
Merge pull request #25 from fightmaster/patch-2

Hi guys!
Fixed the assertion of redirection to handle lowercase headers

A complete implementation should handle it case-insensitively but the
current return value of getResponseHeaders() does not make any assumption
on the case, thus making it harder.