Forum Discussion

jmetzger's avatar
jmetzger
New Contributor
16 years ago

Request buffer size limit

I have been successfully using version 2.5.1 for a long time, but I have run into a problem with a large request message.  I got an immediate response of HTTP/1.1 400 Bad Request.  After some experimentation, I found that as long as the Content-Length value of the request message is 65536 or lower, the request works, but adding one more byte causes the error.

Is there any way to increase the maximum request message size?  I know that many of the messages I will be testing are going to larger than 64K.

Thanks,
Jim

2 Replies

  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    16 years ago
    Hello,

    Could you post the output of your HTTP log? It sounds to me like the server isn't accepting requests larger than 64K and responding with a 400 error whenever a larger request is sent. Could you check if the server has any restrictions of this kind?

    Regards,
    Dain
    eviware.com
  • jmetzger's avatar
    jmetzger
    New Contributor
    16 years ago
    Dain,

    Thanks for responding.  Someone here actually found that it was a series of IIS settings in our server's web.config file that made the difference. In our binding definitions, we needed to set large values for the maxDepth, maxStringContent, maxArrayLength, maxBytesPerRead and maxNameTableCharCount attributes in the readerQuotas element.

    In short, soapUI was simply the messenger relaying the bad news.  All is better now.

    Jim