hey peeps, I was able to use the pact-provider-ver...
# generalj
Jean Paiva
04/14/2023, 8:26 PMhey peeps, I was able to use the pact-provider-verifier for a while now, but this week I had to go through a DELETE endpoint and I notice that things on the provider side froze and I couldn’t see any result. Did anyone see this issue before and know how can I avoid it? This DELETE request has a body on it. I read a little on the matter and I saw this open issue: https://github.com/pact-foundation/pact-js/issues/484
Considering that I am using the agnostic implementation of the provider, is there anything I could do?
t
Timothy Jones
04/15/2023, 12:01 AMYes, you can change the consumer to not send a delete with a body. HTTP doesn’t support this.
👍 1
Timothy Jones
04/15/2023, 12:02 AMcertain clients might support it, and certain servers might understand it. But you can’t be sure.
Timothy Jones
04/15/2023, 12:02 AMAnd the http rfc says they don’t have to support it.
m
Matt (pactflow.io / pact-js / pact-go)
04/15/2023, 1:47 AM
Yep, it's all very vague when you send a body on a DELETE or a GET. Best avoiding it
I've actually seen a case before where a consumer sends a body but the provider ignores it. It's worth checking, because then you know the body is redundant and you can just do what is explicitly supported by the RFC (and frankly, what is standard practice)