nifi-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From indus well <indusw...@gmail.com>
Subject Re: InvokeHTTP Content Type
Date Fri, 04 Dec 2015 21:54:13 GMT
Wow, strange that the Configure Process Properties tab does not look the
same as yours with all the additional properties after Proxy Port:

[image: Inline image 1]

Should I redownload and rebuild?

On Fri, Dec 4, 2015 at 3:44 PM, Joe Percivall <joepercivall@yahoo.com>
wrote:

> Hmm yes it should be. I just tried it and it worked for me. Here is a
> screen shot of my config showing the new property with "Accept"
> "application/json".
>
>
> [image: Inline image]
>
> Also I did a wireshark capture and saw that the request went out the
> proper header.[image: Inline image]
>
>
> - - - - - -
> *Joseph Percivall*
> linkedin.com/in/Percivall
> e: joepercivall@yahoo.com
>
>
>
>
> On Friday, December 4, 2015 4:37 PM, indus well <induswell@gmail.com>
> wrote:
>
>
> I am currently running on 0.4.0-SNAPSHOT which I downloaded and built on
> 11/30. Would it include your change?
>
> On Fri, Dec 4, 2015 at 3:30 PM, Joe Percivall <joepercivall@yahoo.com>
> wrote:
>
> Sorry, what version are you running? Adding the property like that is
> something I added for 0.4.0.
>
> - - - - - -
> Joseph Percivall
> linkedin.com/in/Percivall
> e: joepercivall@yahoo.com
>
>
>
>
> On Friday, December 4, 2015 4:27 PM, indus well <induswell@gmail.com>
> wrote:
>
>
>
> Yes, I passed a header with key "Accept" and value "application/json". I
> followed your instruction and add a new property in the InvokeHTTP process
> called "Accept" and value of "application/json", but I now had an error
> said "'Accept' validated against 'application/json' is invalid because
> 'Accept' is not a supported property."
>
> Did I do something wrong?
>
> Thanks,
>
> Indus
>
>
> On Fri, Dec 4, 2015 at 3:12 PM, Joe Percivall <joepercivall@yahoo.com>
> wrote:
>
> I see, as for the request I'm guessing you mean you pass a header with key
> "Accept" and value "application/json"? If so in the configuration tab for
> the processor properties create a new dynamic one (using the plus in the
> top right) with a key of "Accept" and value of "application/json".
> >
> >You use the "Attributes to Send" property when you already have the
> header value as an attribute of the flowfile and want to send an attribute
> with that name and it's value.
> >
> >Joe
> >
> >- - - - - -
> >Joseph Percivall
> >linkedin.com/in/Percivall
> >e: joepercivall@yahoo.com
> >
> >
> >
> >
> >
> >On Friday, December 4, 2015 4:06 PM, indus well <induswell@gmail.com>
> wrote:
> >
> >
> >
> >Thanks, Joe. My use case involves calling a REST service that returns XML
> response by default. However, it also has option for JSON which I can pass
> "Accept: application/json" along with the request using CURL for example. I
> tried to set that on the "Attributes to Send" property in the InvokeHTTP
> processor, but it did not work. It always returns XML.
> >
> >Thanks,
> >
> >Indus
> >
> >
> >On Fri, Dec 4, 2015 at 2:49 PM, Joe Percivall <joepercivall@yahoo.com>
> wrote:
> >
> >Hello Indus,
> >>
> >>Are you receiving a specific error when you attempt to receive a JSON
> response?
> >>
> >>I can configure an InvokeHTTP processor to GET "
> http://api.randomuser.me/" by just setting the URL and it properly
> receives back a JSON response.
> >>
> >>Joe
> >>
> >>
> >>- - - - - -
> >>Joseph Percivall
> >>linkedin.com/in/Percivall
> >>e: joepercivall@yahoo.com
> >>
> >>
> >>
> >>
> >>
> >>On Friday, December 4, 2015 3:27 PM, indus well <induswell@gmail.com>
> wrote:
> >>
> >>
> >>
> >>Hi All:
> >>
> >>How would I configure the InvokeHTTP processor to receive content type
> of JSON response?
> >>
> >>Thanks,
> >>
> >>Indus Well
> >>
> >
>
>
>
>
>

Mime
View raw message