Closed mefellows closed 1 year ago
👋 Hi! The 'smartbear-supported' label has just been added to this issue, which will create an internal tracking ticket in PactFlow's Jira (PACT-1173). We will use this to prioritise and assign a team member to this task. All activity will be public on this ticket. For now, sit tight and we'll update this ticket once we have more information on the next steps.
See our documentation for more information.
I believe this is fixed now, closing.
1.0.1
0.4.5
Given the following test that specifies multiple accept header values:
it fails with:
See repro: https://github.com/pact-foundation/pact-reference/compare/repro/pact-js-issue-1031?expand=1
You can run the test with
cargo test mock_server_passing_validation -- --exact
Relates to https://github.com/pact-foundation/pact-js/issues/964 and https://github.com/pact-foundation/pact-js/issues/1061
FFI Related Issue
The FFI seems to behave slightly differently.
Given this JS example:
The failure is:
It seems to be concatenating all of comma separated values when a multi-valued header is defined as a string, but not when each header value is independently passed in. The values are being set via the
pactffi_with_header_v2
method.TRACE level log
I've confirmed the JS library is sending an unadulterated header string. There is an entry in the log I extracted:
The rust logs are: