Fix for request matcher missing query string differences

The submitted pull request fixes an issue where the request matcher doesn't take into account the query string of the request being made.

If a fixture exists that covers "http://example.com/search?query=first", the same fixture response would be used for "http://example.com/search?query=second", "http://example.com/search?query=third", etc.