Limitation of the received content in the response body

Hello again!
The problem is that the received content in the response of the API used does not exceed 23489 bytes. There are no restrictions on the application and server side. There are no restrictions when sending the same request to the Postman. What could be the matter, please tell me?

<scala.version>2.13.11</scala.version>
<gatling.version>3.9.5</gatling.version>
gatling-maven-plugin-demo-scala
4.6.0

Request example
the application uses json-rpc

  val gettingDocuments = http("/api/v1/docType.json")
    .post("/api/v1/docType.json")
    .body(StringBody(
      """
{
        "id": 276,
        "jsonrpc": "2.0",
        "method": "fetchAll",
        "params": {
          "request": {
            "page": 0,
            "size": 150,
            "sort": {
              "createdAt": "DESC"
            },
            "filter": [
              {
                "name": "docStatus",
                "value": [
                  "IN_PROCESS",
                  "FINISHED",
                  "DENIED",
                  "TRANSITION_TO_INTRODUCED",
                  "TRANSITION_TO_ENTRANCE_CONTROL",
                  "TRANSITION_TO_REVIEWED",
                  "TRANSITION_TO_CANCELLED"
                ],
                "criteria": "NOT_IN"
              },
              {
                "name": "condition",
                "value": [
                  "REGISTERED"
                ],
                "criteria": "NOT_IN"
              }
            ]
          }
        }
      }
"""))
    .check(status is 200)

Headers

val commonHeaders = Map(
    //"Content-Type" -> "application/json; charset=UTF-8",
    "Accept" -> "*/*",
    "Authorization" -> "<jwtToken>",
    "Accept-Encoding"  -> "gzip, deflate, br",
    "Connection" -> "keep-alive",
    "Host" -> "isupd-gateway.api.akkuyu.test.csp",
    "User-Agent" -> "Chrome/119.0.0.0, Safari/537.36",
    //"Version" -> "HTTP1/.1"
  )

Скриншот 04-12-2023 181450

Maybe the problem is related to my neighboring topic

Please first upgrade to Gatling 3.9.6. You’re using an obsolete version. Maybe this is a bug that’s been fixed for a long time.

Updated Gatling, but the problem persists unfortunately :smiling_face_with_tear:

Could you please provide a way to reproduce your issue?

Honestly, I don’t think the issue is with Gatling. There’s a very good chance that you’re not exactly passing the same request with Postman and with Gatling (different headers or different payload, resulting in a different response).

Hi @Yujin,

From your screenshot, your server response contains the header content-length: 23489.
Maybe you have a limit in your server or in any proxy in between.

Cheers!

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.