GET with body sends as query string

I have the following contract for a consumer. The request works when sending it to the server using Postman.

When the pact provider tries to verify it fails. The body is sent in the query string and not in the body of the GET request as expected.

Using the latest version of PactNet.

{
  "consumer": {
    "name": "Source System"
  },
  "provider": {
    "name": "Event API"
  },
  "interactions": [
    {
      "description": "A GET request with event filters",
      "providerState": "default state",
      "request": {
        "method": "get",
        "path": "/events",
        "headers": {
          "Content-Type": "application/json; charset=utf-8"
        },
        "body": {
          "filters": [
            {
              "type": "state",
              "source": "logs"
            },
            {
              "type": "information",
              "source": "memory"
            }
          ]
        }
      },
      "response": {
        "status": 200,
        "headers": {
          "Content-Type": "application/json; charset=utf-8"
        },
        "body": {
          "data": [
            {
              "id": 1,
              "event": "init",
            },
            {
              "id": 2,
              "event": "start",
            }
          ]
        }
      }
    }
  ],
  "metadata": {
    "pactSpecification": {
      "version": "2.0.0"
    }
  }
}

[neilcampbell]

@Nexith That’s going to be the ruby core doing that. Typically a body in a GET requests is not a good idea, purely because the HTTP 1.1 spec had language to indicate it should not be supported on the server side. I know now the spec has been amended, but still you run into compatibility issues like this one. I’d recommend changing your API to accept query params instead and updating the pact to use query, rather than body.

[adamrodger]

Should be fixed in 4.x with the move to Rust core instead of Ruby (or at least it’ll be broken in a differnt way 😁 )