Alex Tsibulya

Content-Type matching is too strict / doesn't follow matcher specification

2

Given the pact JSON with `term` matcher on `Content-Type` header: ```json "response": { "status": 200, "headers": { "Content-Type": "text/plain" }, "body": "fake-header.fake-token.fake-signature", "matchingRules": { "$.headers.Content-Type": { "match": "regex", "regex": "^text\\/plain"...

Given the following pact JSON: ```json "headers": { "Content-Type": "application/json", "Set-Cookie": "auth=fake-token; HttpOnly" }, "body": {}, "matchingRules": { "$.headers.Content-Type": { "match": "regex", "regex": "^application\\/json(;|$)" }, "$.headers.Set-Cookie": { "match": "regex", "regex":...