Showing results for 
Search instead for 
Did you mean: 

ReadyAPI 2.4.0 -- 408 error with large JSON payload


ReadyAPI 2.4.0 -- 408 error with large JSON payload

I upgraded to ReadyAPI 2.4.0 a couple days ago and am encountering an issue using large JSON payloads. With the latest release, I am getting 408 errors when sending large JSON requests (this took 1 minute before I got the error):


HTTP/1.1 408 Request body incomplete
Date: Wed, 13 Jun 2018 18:18:21 GMT
Content-Type: text/html; charset=UTF-8
Connection: close
Cache-Control: no-cache, must-revalidate
Timestamp: 14:18:21.171

The request body did not contain the specified number of bytes. Got 0, expected 319,026    



When I run this exact test scenario using ReadyAPI 2.3.0, it works just fine (took 1.5 seconds):


HTTP/1.1 200 OK
Expires: 0
Cache-Control: no-cache, no-store, max-age=0, must-revalidate
X-Powered-By: Undertow/1
Server: WildFly/9
X-XSS-Protection: 1; mode=block
Pragma: no-cache
X-Frame-Options: SAMEORIGIN
Date: Wed, 13 Jun 2018 18:25:04 GMT
Connection: keep-alive
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json;charset=UTF-8



I've been doing some experimenting by adding/removing chunks of the JSON and this only seems to occur with very large JSON payloads in 2.4.0. Prior to this, I had been using 2.3.0 for months and have never had issues with large payloads, in fact I didn't even know what a 408 error was until today. I definitely think something has changed between 2.3.0 and 2.4.0. Is anyone experiencing the same?

Community Hero

Re: ReadyAPI 2.4.0 -- 408 error with large JSON payload

Couple of options for you:

1. Continue to use earlier version as there is no issue for you.
2. Report the issue with customer care using below link:

Here is a thread which helps on when to upgrade the software, hoping that it helps.
Top Kudoed Authors
Are You In?

Meet the Community Leaders!

SmartBear Connect is an excellent opportunity for training, in-person support, and networking.