newman
newman copied to clipboard
add feature to limit the response body size newman can process instead of running out of memory
Newman Version (can be found via newman -v): 5.2.0 OS details (type, version, and architecture): Are you using Newman as a library, or via the CLI? cli Did you encounter this recently, or has this bug always been there: Expected behaviour: Command / script used to run Newman: Sample collection, and auxiliary files (minus the sensitive details): Screenshots (if applicable):
@yusong0926 Can you elaborate this a little please??
Ooh! This will be pretty interesting to implement. The core support needs to be in the stream processing of the postman-request library and then the corresponding configuration needs to be carried from newman via runtime to postman-request.
@codenirvana Thoughts?
I'm looking into how this can be implemented.
Also, importantly --timeout-request <n> doesn't help here because it simply doesn't seem to include the download time for a heavy response. It only works if the server keeps newman waiting for a long time without sending response, but not if it keeps sending a long response.
Hi, I'm getting this error, there is any work around for request too large? Thanks!
Error: Server responded to https://............testrail.io/index.php?/api/v2/add_results_for_cases/.. with status code 413: