Sofia Sedloff
04/15/2024, 2:42 PMstatus: 100-199
. Does Pact handle interactions with 100-199 status codes?Sofia Sedloff
04/15/2024, 2:45 PM.willRespondWith({
status: 150,
headers: {
'Content-Type': 'application/json',
},
body: expectedMessage,
});
Mock server response:
Response {
[Symbol(realm)]: null,
[Symbol(state)]: {
aborted: false,
rangeRequested: false,
timingAllowPassed: true,
requestIncludesCredentials: true,
type: 'default',
status: 500,
...
Matt (pactflow.io / pact-js / pact-go)
1xx
are supported by the underlying infrastructure: https://github.com/hyperium/hyper/issues/2565Matt (pactflow.io / pact-js / pact-go)
Sofia Sedloff
04/16/2024, 8:53 PM2024-04-16T20:51:24.471821Z WARN tokio-runtime-worker encode_headers: hyper::proto::h1::role: response with 1xx status code not supported
2024-04-16T20:51:24.471868Z DEBUG tokio-runtime-worker hyper::proto::h1::io: flushed 94 bytes
2024-04-16T20:51:24.471882Z TRACE tokio-runtime-worker hyper::proto::h1::conn: State::close()
2024-04-16T20:51:24.471892Z TRACE tokio-runtime-worker hyper::proto::h1::conn: flushed({role=server}): State { reading: Closed, writing: Closed, keep_alive: Disabled, error: hyper::Error(User(UnsupportedStatusCode)) }
Matt (pactflow.io / pact-js / pact-go)