topic [resolved] 411 Length Required Exception in tRestClient Component in Talend Studio

[resolved] 411 Length Required Exception in tRestClient Component

_AnonymousUser — Wed, 10 Sep 2014 13:59:21 GMT

Hi All,
I got an error while sending a post request using tRestClient with the content-type and accept type are application/json.But when I try to send the same request with tRest component it's working fine.what could be the reason why I'm not able do the same request with the tRestClient component?
Because in tRest component I only get the error code but with the tRestClient component I also get error message including error code.So I can handle the exceptions very easily.
I tried with and wthout Content-Length header and in both the cases getting the same exception.
Attached the screen shot for your reference.
Can any one please help me on this?

Out bound message on console :

In bound message on console :

Thanks
Sayagoud Ravelly

Re: [resolved] 411 Length Required Exception in tRestClient Component

Anonymous — Wed, 10 Sep 2014 16:30:39 GMT

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

Re: [resolved] 411 Length Required Exception in tRestClient Component

_AnonymousUser — Thu, 11 Sep 2014 06:19:40 GMT

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

Hi,
I'm able to do the same request with tRest component but why not with tRestClient?

HTTPUrlConnection starting using the chunked encoding which does not support Content-Length

I also tried by sending the payload with out Content-Length header but I got the same exception
is there any workaround for this exception with tRestClient?

Re: [resolved] 411 Length Required Exception in tRestClient Component

Anonymous — Thu, 11 Sep 2014 07:19:39 GMT

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

Re: [resolved] 411 Length Required Exception in tRestClient Component

_AnonymousUser — Thu, 11 Sep 2014 07:51:29 GMT

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

Hi Shong,
Thanks for your reply.
Do we have any other way to get the error code and error message with the post request other than tRest and tRestClient?

Re: [resolved] 411 Length Required Exception in tRestClient Component

Anonymous — Fri, 12 Sep 2014 08:23:57 GMT

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

Re: [resolved] 411 Length Required Exception in tRestClient Component

_AnonymousUser — Fri, 12 Sep 2014 09:11:03 GMT

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

Hi Shong,
If I use the tRestClient component it is returning the error code and error message details but it is throwing me the 411 Length Required exception because of chunked encoding.
Do we have any other component to handle restful requests ,which will provide me the error code and error message details like tRestClient?.

Re: [resolved] 411 Length Required Exception in tRestClient Component

_AnonymousUser — Mon, 15 Sep 2014 15:00:29 GMT

Hi All,
I resolved the issue with tRestClient by installing the latest version of Talend Open Studio :5.6.0 M4 (test version ) and updated the component accordingly in my previous version.
In new component there is an option called : Disable chunked encoding and we need to check this option as shown like below.

Re: [resolved] 411 Length Required Exception in tRestClient Component

hamdi_bourbia — Fri, 01 Oct 2021 14:44:24 GMT

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 ...

Re: [resolved] 411 Length Required Exception in tRestClient Component

aksharma — Wed, 06 Apr 2022 08:05:55 GMT

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

Re: [resolved] 411 Length Required Exception in tRestClient Component

ChaitraCP — Tue, 16 Aug 2022 06:27:05 GMT

Im facing same issue. Is there any resolution for this.

Re: [resolved] 411 Length Required Exception in tRestClient Component

S1660598179 — Mon, 03 Jun 2024 13:35:00 GMT

I am facing same issue. Is there any work around to avoid content length error? It is throwing content length must be specified.