#377 fix the issue in matchDomain method
#377 fix the issue in matchDomain method
#377 fix the issue in matchDomain method
Consider an extreme case in the test:
Cookie domain: .127.0.0.1
Actual domain: 127.0.0.1
This cookie shouldn't be matched
dispatch now returns the event that was created
Removed a test case that won't happen in real world where made #378 failed by testing
Guessing when to use DefaultAggregator vs PhpAggregator when parsing query strings. Address #379
Try it again. When the domain is an IP and is identical from the cookie domain, it should match, however if the cookie domain is something like .127.0.0.1, it shouldn't match
Merge pull request #381 from guzzle/querystring-guess-aggregator

Guessing when to use DefaultAggregator vs PhpAggregator when parsing que...
Finishing up the cookie domain matching fixes
Merge branch 'master' into cookie-fix
Adding an event based way to create custom domain models from service description responses
Making injecting the result into the event more explicit and automatically stop propagation
Renaming event to better fit with other events
Removing a couple of unnecessary checks in curlmulti
Updating perf serve to consume input string
Fixing content-length for test server perf response
Moving perf endpoint to guzzle-server. Updating server controls
Fixed Collection access in Oauth Plugin

A Collection was being accessed with a built-in array function.
Merge pull request #383 from squirly/patch-1

Fixed Collection access in Oauth Plugin