Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi
This is most likely due to the JSON payload exceeding a certain limit and HTTPUrlConnection starting using the chunked encoding which does not support Content-Length. Generally speaking the chunked encoding is more efficient for transferring the large payloads. Some legacy servers (non-Apache CXF based) can not deal with the chunked encoding and fail.
This issue has been raised recently and tRESTClient will allow disabling the chunked encoding in the coming ESB Studio release
HTH, Sergey
HTTPUrlConnection starting using the chunked encoding which does not support Content-Length
Hi
As sberyozkin said, there was a issue on the tRestClient component right now, this issue will be fixed in the next release, it will allow disabling the cunhked encoding.
Best regards
Shong
Do we have any other way to get the error code and error message with the post request other than tRest and tRestClient?
Do we have any other way to get the error code and error message with the post request other than tRest and tRestClient?
Sorry, I don't understand your question, can you please explain it with more details?
Best regards
Shong
I do have Talend Cloud Real-time big data plateform 7.3.1, and the option Disable chunked encoding in the tRestClient. But while having this option set (no chunked encoding) I still have the HTTP 411 Length Required error ...
I am also getting same in talend 7.3.1 do any one find any solutio to this.
HTTP Error 411. The request must be chunked or have a content length.
Thanks
Ashish