You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@nifi.apache.org by "Vincent, Mike" <mv...@mitre.org> on 2019/01/30 17:57:32 UTC
RE: [EXT] Unexpected char exception in InvokeHTTP
Are you sure you aren’t using “https “ (notice the space after the ‘s’)? Since 0x20 is an ASCII space, I wonder if that’s what’s causing your issue?
Cheers,
Michael J. Vincent
Lead Network Systems Engineer | The MITRE Corporation | Network Technology & Security (T864) | +1 (781) 271-8381
From: l vic <lv...@gmail.com>
Sent: Wednesday, January 30, 2019 12:01 PM
To: users@nifi.apache.org
Subject: [EXT] Unexpected char exception in InvokeHTTP
I am using InvokeHTTP with StandardRestrictedSSLContextService 1.6.0 to perform REST call with Proxy Type = https
On some systems it just works, on other systems i have the following error:
InvokeHTTP[id=d3f4b6c9-1204-3e1a-1373-431715543d24] Routing to Failure due to exception: Unexpected char 0x20 at 5 in header name: Proxy Type: java.lang.IllegalArgumentException: Unexpected char 0x20 at 5 in header name: Proxy Type
This exception doesn't seem to appear anywhere in logs, any idea how to troubleshoot this problem, or what can cause it?
Thank you
Re: [EXT] Unexpected char exception in InvokeHTTP
Posted by l vic <lv...@gmail.com>.
I've been wondering about it myself but tweaking that value doesn't change
anything.... Yes I made sure it's "https", not "https "....
On Wed, Jan 30, 2019 at 12:57 PM Vincent, Mike <mv...@mitre.org> wrote:
> Are you sure you aren’t using “https “ (notice the space after the ‘s’)?
> Since 0x20 is an ASCII space, I wonder if that’s what’s causing your issue?
>
>
>
> Cheers,
>
>
>
> Michael J. Vincent
>
> Lead Network Systems Engineer | The MITRE Corporation | Network Technology
> & Security (T864) | +1 (781) 271-8381
>
>
>
> *From:* l vic <lv...@gmail.com>
> *Sent:* Wednesday, January 30, 2019 12:01 PM
> *To:* users@nifi.apache.org
> *Subject:* [EXT] Unexpected char exception in InvokeHTTP
>
>
>
> I am using InvokeHTTP with StandardRestrictedSSLContextService 1.6.0 to
> perform REST call with Proxy Type = https
>
>
>
>
>
> On some systems it just works, on other systems i have the following error:
>
>
>
> InvokeHTTP[id=d3f4b6c9-1204-3e1a-1373-431715543d24] Routing to Failure due
> to exception: Unexpected char 0x20 at 5 in header name: Proxy Type:
> java.lang.IllegalArgumentException: Unexpected char 0x20 at 5 in header
> name: Proxy Type
>
>
>
> This exception doesn't seem to appear anywhere in logs, any idea how to
> troubleshoot this problem, or what can cause it?
>
> Thank you
>
Re: [EXT] Unexpected char exception in InvokeHTTP
Posted by l vic <lv...@gmail.com>.
Can someone explain what's this property for in the first place? Is it
needed for SSLContextService? I didn't find it in documentation...
On Wed, Jan 30, 2019 at 12:57 PM Vincent, Mike <mv...@mitre.org> wrote:
> Are you sure you aren’t using “https “ (notice the space after the ‘s’)?
> Since 0x20 is an ASCII space, I wonder if that’s what’s causing your issue?
>
>
>
> Cheers,
>
>
>
> Michael J. Vincent
>
> Lead Network Systems Engineer | The MITRE Corporation | Network Technology
> & Security (T864) | +1 (781) 271-8381
>
>
>
> *From:* l vic <lv...@gmail.com>
> *Sent:* Wednesday, January 30, 2019 12:01 PM
> *To:* users@nifi.apache.org
> *Subject:* [EXT] Unexpected char exception in InvokeHTTP
>
>
>
> I am using InvokeHTTP with StandardRestrictedSSLContextService 1.6.0 to
> perform REST call with Proxy Type = https
>
>
>
>
>
> On some systems it just works, on other systems i have the following error:
>
>
>
> InvokeHTTP[id=d3f4b6c9-1204-3e1a-1373-431715543d24] Routing to Failure due
> to exception: Unexpected char 0x20 at 5 in header name: Proxy Type:
> java.lang.IllegalArgumentException: Unexpected char 0x20 at 5 in header
> name: Proxy Type
>
>
>
> This exception doesn't seem to appear anywhere in logs, any idea how to
> troubleshoot this problem, or what can cause it?
>
> Thank you
>