Open vasile21 opened 8 months ago
I can't replicate this. If I run the given code against the master version of Pact-JVM, I get:
"request": {
"headers": {
"Content-Security-Policy": "default-src: 'none'; frame-ancestors 'none'; base-uri 'self'",
"strict-transport-security": "max-age=3600; includeSubDomains; reload"
},
"method": "POST",
"path": "/path"
},
"response": {
"headers": {
"Content-Security-Policy": "default-src: 'none'; frame-ancestors 'none'; base-uri 'self'",
"strict-transport-security": "max-age=3600; includeSubDomains; reload"
},
"status": 200
}
and the logs from the test:
http-outgoing-1 << HTTP/1.1 200 OK
http-outgoing-1 << strict-transport-security: max-age=3600; includeSubDomains; reload
http-outgoing-1 << Date: Tue, 14 Nov 2023 22:49:25 GMT
http-outgoing-1 << Transfer-encoding: chunked
http-outgoing-1 << Content-Security-Policy: default-src: 'none'; frame-ancestors 'none'; base-uri 'self'
Hi I am migrating to latest pact-consumer library:
My PactDsl creation looks like:
In the older version of pact headers that contained semicolon were handled correctly in pact file:
Pact file after the upgrade contains invalid values for headers as can be seen below:
Pact consumer logs:
Could you let me know if this will be fixed or if there is any workaround for this issue?