Error on InvokeHTTP
I have a text flowfile that I am trying to send to a translation service on a remote EC2 instance from my nifi insurance on my EC2. I am failing with only this somewhat-cryptic error: InvokeHTTP[id=a72e1727-3da0-1d6c-164b-e43c1426fd97] Routing to Failure due to exception: Unexpected char 0x20 at 6 in header name: Socket Write Timeout: java.lang.IllegalArgumentException: Unexpected char 0x20 at 6 in header name: Socket Write Timeout What does this mean? Is what I am sending from InvokeHTTP employing a header formatted in a way that is not expected? I am using an InvokeHTTP version 1.16.3. Has anyone experienced a similar error?
Re: Error on InvokeHTTP
it seems charset issue. if it is a json add charset=utf-8 On Fri, Jan 12, 2024, 6:33 PM James McMahon wrote: > I have a text flowfile that I am trying to send to a translation service > on a remote EC2 instance from my nifi insurance on my EC2. I am failing > with only this somewhat-cryptic error: > > InvokeHTTP[id=a72e1727-3da0-1d6c-164b-e43c1426fd97] Routing to Failure > due to exception: Unexpected char 0x20 at 6 in header name: Socket Write > Timeout: java.lang.IllegalArgumentException: Unexpected char 0x20 at 6 in > header name: Socket Write Timeout > > > What does this mean? Is what I am sending from InvokeHTTP employing a header > formatted in a way that is not expected? > > > I am using an InvokeHTTP version 1.16.3. > > Has anyone experienced a similar error? > > > > >
Re: Error on InvokeHTTP
0x20 is a space. Maybe that's somewhere in your header? On 1/12/2024 4:33 PM, James McMahon wrote: I have a text flowfile that I am trying to send to a translation service on a remote EC2 instance from my nifi insurance on my EC2. I am failing with only this somewhat-cryptic error: InvokeHTTP[id=a72e1727-3da0-1d6c-164b-e43c1426fd97] Routing to Failure due to exception: Unexpected char 0x20 at 6 in header name: Socket Write Timeout: java.lang.IllegalArgumentException: Unexpected char 0x20 at 6 in header name: Socket Write Timeout What does this mean? Is what I am sending from InvokeHTTP employing a header formatted in a way that is not expected? I am using an InvokeHTTP version 1.16.3. Has anyone experienced a similar error? -- This email has been checked for viruses by AVG antivirus software. www.avg.com
Re: Error on InvokeHTTP
Juan, to do as you suggest would I set Content-Encoding in the processor configuration to utf-8? Does that achieve this? Joe O., I don't see any property in the Properties of the InvokeHTTP processor that allows me to expect and handle spaces in the header. I also don't explicitly create a header: I GenerateFlowFile with a body that is english text. I IdentifyMimeType. I send that through InvokeHTTP. On Fri, Jan 12, 2024 at 5:04 PM Juan Pablo Gardella < gardellajuanpa...@gmail.com> wrote: > it seems charset issue. if it is a json add charset=utf-8 > > On Fri, Jan 12, 2024, 6:33 PM James McMahon wrote: > >> I have a text flowfile that I am trying to send to a translation service >> on a remote EC2 instance from my nifi insurance on my EC2. I am failing >> with only this somewhat-cryptic error: >> >> InvokeHTTP[id=a72e1727-3da0-1d6c-164b-e43c1426fd97] Routing to Failure >> due to exception: Unexpected char 0x20 at 6 in header name: Socket Write >> Timeout: java.lang.IllegalArgumentException: Unexpected char 0x20 at 6 in >> header name: Socket Write Timeout >> >> >> What does this mean? Is what I am sending from InvokeHTTP employing a header >> formatted in a way that is not expected? >> >> >> I am using an InvokeHTTP version 1.16.3. >> >> Has anyone experienced a similar error? >> >> >> >> >>
