transfer-encoding:chunked for WS request
I am using soapUI 2.5.1 to test uploading documents to a WS using MTOM. By default I am seeing very high memory usage (10 X doc size) in the java heap both in soapUI client, and in the java server. ...
Forum Discussion
Hello,
I've looked in to this a bit more, and have found a way to force chunking. An idea now is to remove the checkbox to disable chunking in the HTTP Preferences, and replace it with an integer value where you can specify a threshold request size. Any request larger than the value will be chunked and any request smaller will not. Setting this to 0 would cause all requests to use chunking and setting it to -1 would completely disable chunking. What do you think of this approach, would it suit your needs well? If you have any other ideas that you think would be better, please let us know.
Regards,
Dain
eviware support
I've looked in to this a bit more, and have found a way to force chunking. An idea now is to remove the checkbox to disable chunking in the HTTP Preferences, and replace it with an integer value where you can specify a threshold request size. Any request larger than the value will be chunked and any request smaller will not. Setting this to 0 would cause all requests to use chunking and setting it to -1 would completely disable chunking. What do you think of this approach, would it suit your needs well? If you have any other ideas that you think would be better, please let us know.
Regards,
Dain
eviware support
