For a legacy SOAP webservice we have to send requests and receive responses using deflate content-encoding.
Example request headers used in the request:
SOAPAction: "getData"
Accept-Encoding: deflate
Content-Encoding: deflate
Content-Type: text/xml; charset=utf-8
Unfortunately, requests with deflate content-encoding generate a response code 500:
HTTP/1.1 500 Internal Server Error
Server: Apache-Coyote/1.1
Content-Length: 0
Date: Fri, 24 Apr 2015 13:35:07 GMT
Connection: close
We tested this request with NeoLoad 5, SoapUI 5.x and SoapUI 4.x and discovered that only SoapUI 4.x managed to successfully send the request and receive a response.
Is deflated encoding supported in NeoLoad 5? If yes, what may be the cause of this error? SoapUI 4.x seems to handle the exact request just fine.
NeoLoad does not support the deflate content-encoding for the requests but it does support it for the responses.
Even Gzip content-encoding on requests is not supported till NeoLoad 5.0.5 (not available yet). It will be supported by default in the next NeoLoad version too. Again it only concerns request content and not responses.