I have been using NeoLoad 5.1.4 to test a web page making https POST request to a web server as text content. When I have default headers and NeoLoad is adding an additional header "Content-Length: 135" and it is returning http response 200 OK. But actual client is has "Transfer-Encoding:chunked" in the request header, so when "Transfer-Encoding:chunked" was added in NeoLoad it is throwing the following error.
Error detected by NeoLoad
Error Code: NL-NETWORK-01 Message: Network error: An IO error occurred sending the request. Details: org.apache.commons.httpclient.NoHttpResponseException: The server atom.qa.boomi.com failed to respond
Please refer to the documentation for further details and advice
It is seems like some sort of encoding issue. Can any one throw light on using "Transfer-Encoding:chunked" header in NeoLoad web script?
I believe the handling of the "Transfer-Encoding:chunked" is something that has been identified in 5.2.2, and will be fixed in the official release of 5.2.3. This should be out by the end of August 2016, possibly.
Did you find this useful ?
100% of users found this answer useful
