Re: InvokeHTTP : how to set a bearer token auth

1.16.0 will provide integration between the OAuth2TokenProvider controller service and InvokeHTTP so this will all be OBE at that point. On Fri, Mar 4, 2022 at 9:38 AM Jim Halfpenny wrote: > Hi Nicola, > The bearer token is set in the Authorization: header of the HTTP request. > What

Re: InvokeHTTP : how to set a bearer token auth

token value. It’s good practice to define the token as a parameter and reference it using the #{param_name} syntax to make it easier to manage. Kind regards, Jim > On 4 Mar 2022, at 13:52, Nicola Biadene > wrote: > > Dear all, > > how can I set a bearer token on a Invok

Re: InvokeHTTP : how to set a bearer token auth

can I set a bearer token on a InvokeHTTP operator? > > I cannot find documentation and a field referring to this parameter. > > > Regards. > > > Nicola Biadene > Software Engineer > nicola.biad...@targatelematics.com <mailto:nicola.biad...@targatelematics.com> &

InvokeHTTP : how to set a bearer token auth

Dear all, how can I set a bearer token on a InvokeHTTP operator? I cannot find documentation and a field referring to this parameter. Regards. Nicola Biadene Software Engineer nicola.biad...@targatelematics.com<mailto:nicola.biad...@targatelematics.com> [/Users/video/Desktop/Schermat

Re: Secure parameters in invokeHttp header

Hello, Since the dynamic properties of InvokeHttp are not marked as sensitive properties, there currently isn't a way to add a sensitive header value. There is a JIRA to improve this experience - https://issues.apache.org/jira/browse/NIFI-7310 Thanks, Bryan On Thu, Nov 5, 2020 at 11:02 AM

Secure parameters in invokeHttp header

Hi all, I am looking for options on how to secure parameters passed in the header for this processor, looks like it currently has it as plain text in the processor. Whoever has access to the system can grab and use it. How can I restrict this? -- Regards, Midhun Mohan

RE: Make invokehttp to process faster to process more than 20k records

Unsubscribe -Original Message- From: Midhun Mohan Sent: Wednesday, March 18, 2020 8:29 AM To: dev@nifi.apache.org Subject: Re: Make invokehttp to process faster to process more than 20k records Hey Mike , I meant like when I try posting that many records it is taking bit time. Just

Re: Make invokehttp to process faster to process more than 20k records

it is > taking > > > bit time. Just checking did you tweak around the thread count and what > is > > > your instance size. CPU and RAM > > > > > > On Wed, 18 Mar 2020 at 18:57, Mike Thomsen > > wrote: > > > > > > &

Re: Make invokehttp to process faster to process more than 20k records

rote: > > > Hey Mike , I meant like when I try posting that many records it is taking > > bit time. Just checking did you tweak around the thread count and what is > > your instance size. CPU and RAM > > > > On Wed, 18 Mar 2020 at 18:57, Mike Thomsen > wrote: > > &

Re: Make invokehttp to process faster to process more than 20k records

CPU and RAM > > On Wed, 18 Mar 2020 at 18:57, Mike Thomsen wrote: > > > By setting the HTTP verb to POST in InvokeHTTP. > > > > On Wed, Mar 18, 2020 at 1:29 AM Midhun Mohan > > wrote: > > > > > How did you post 50k flowfiles, that is what am lookin

Re: Make invokehttp to process faster to process more than 20k records

> your instance size. CPU and RAM > > On Wed, 18 Mar 2020 at 18:57, Mike Thomsen wrote: > > > By setting the HTTP verb to POST in InvokeHTTP. > > > > On Wed, Mar 18, 2020 at 1:29 AM Midhun Mohan > > wrote: > > > > > How did you post 50k flowfiles

Re: Make invokehttp to process faster to process more than 20k records

it is taking bit time. Just checking did you tweak around the thread count and what is your instance size. CPU and RAM On Wed, 18 Mar 2020 at 18:57, Mike Thomsen wrote: > By setting the HTTP verb to POST in InvokeHTTP. > > On Wed, Mar 18, 2020 at 1:29 AM Midhun Mohan > wrote: > > >

Re: Make invokehttp to process faster to process more than 20k records

Hey Mike , I meant like when I try posting that many records it is taking bit time. Just checking did you tweak around the thread count and what is your instance size. CPU and RAM On Wed, 18 Mar 2020 at 18:57, Mike Thomsen wrote: > By setting the HTTP verb to POST in InvokeHTTP. > > On

Re: Make invokehttp to process faster to process more than 20k records

By setting the HTTP verb to POST in InvokeHTTP. On Wed, Mar 18, 2020 at 1:29 AM Midhun Mohan wrote: > How did you post 50k flowfiles, that is what am looking for > > On Wed, 18 Mar 2020 at 02:36, Mike Thomsen wrote: > > > That's probably a lot of the issue, especially

Re: Make invokehttp to process faster to process more than 20k records

s with 4k of JSON in them to an Express hello world app > and it was able to respond to 50k flowfiles in under 10s using InvokeHttp > with only 3 threads. All on my MacBook Pro. > > On Tue, Mar 17, 2020 at 4:54 PM Midhun Mohan > wrote: > > > Endpoint does execu

Re: Make invokehttp to process faster to process more than 20k records

That's probably a lot of the issue, especially if it's an evented service like a Node service running with one thread. I just did a simple test by posting 50k flowfiles with 4k of JSON in them to an Express hello world app and it was able to respond to 50k flowfiles in under 10s using InvokeHttp

Re: Make invokehttp to process faster to process more than 20k records

> On Tue, Mar 17, 2020 at 3:55 PM Midhun Mohan > wrote: > > > Yeah the endpoint which am sending right now has plenty of resources > > available. Only thing is I need to send more records > > > > On Wed, 18 Mar 2020, 1:23 am Chad Zobrisky, wrote: > > >

Re: Make invokehttp to process faster to process more than 20k records

o send more records > > On Wed, 18 Mar 2020, 1:23 am Chad Zobrisky, wrote: > > > I have not test throughput of InvokeHTTP so am not sure what the maximum > > is, but can give some general guidance. > > > > 1kb isn't bad. For bottleneck I'd use top, iotop, etc. to

Re: Make invokehttp to process faster to process more than 20k records

gt; > > yes, > > > > > to which number? How many cores do you have on NiFi? > > > > > > > > > > Thanks > > > > > > > > > > Le mar. 17 mars 2020 à 20:55, Midhun Mohan > > > a > > > > > écrit : > &g

Re: Make invokehttp to process faster to process more than 20k records

> yes, > > > > to which number? How many cores do you have on NiFi? > > > > > > > > Thanks > > > > > > > > Le mar. 17 mars 2020 à 20:55, Midhun Mohan > a > > > > écrit : > > > > > > > > > Yeah th

Re: Make invokehttp to process faster to process more than 20k records

> > > > > > Le mar. 17 mars 2020 à 20:55, Midhun Mohan a > > > écrit : > > > > > > > Yeah the endpoint which am sending right now has plenty of resources > > > > available. Only thing is I need to send more records > > > > &g

Re: Make invokehttp to process faster to process more than 20k records

; > > > Thanks > > > > Le mar. 17 mars 2020 à 20:55, Midhun Mohan a > > écrit : > > > > > Yeah the endpoint which am sending right now has plenty of resources > > > available. Only thing is I need to send more records > > > > > &g

Re: Make invokehttp to process faster to process more than 20k records

> > > > On Wed, 18 Mar 2020, 1:23 am Chad Zobrisky, wrote: > > > > > I have not test throughput of InvokeHTTP so am not sure what the > maximum > > > is, but can give some general guidance. > > > > > > 1kb isn't bad. For bottleneck I'd u

Re: Make invokehttp to process faster to process more than 20k records.

ds > > > > On Wed, 18 Mar 2020, 1:23 am Chad Zobrisky, wrote: > > > > > I have not test throughput of InvokeHTTP so am not sure what the > maximum > > > is, but can give some general guidance. > > > > > > 1kb isn't bad. For bottleneck I'd u

Re: Make invokehttp to process faster to process more than 20k records

I need to send more records > > On Wed, 18 Mar 2020, 1:23 am Chad Zobrisky, wrote: > > > I have not test throughput of InvokeHTTP so am not sure what the maximum > > is, but can give some general guidance. > > > > 1kb isn't bad. For bottleneck I'd use top, iotop, et

Re: Make invokehttp to process faster to process more than 20k records

Yeah the endpoint which am sending right now has plenty of resources available. Only thing is I need to send more records On Wed, 18 Mar 2020, 1:23 am Chad Zobrisky, wrote: > I have not test throughput of InvokeHTTP so am not sure what the maximum > is, but can give some general gu

Re: Make invokehttp to process faster to process more than 20k records

I have not test throughput of InvokeHTTP so am not sure what the maximum is, but can give some general guidance. 1kb isn't bad. For bottleneck I'd use top, iotop, etc. to figure out system resources usage while your flow is running. You should be able to increase both your nifi count by more

Re: Make invokehttp to process faster to process more than 20k records

gt; On Tue, 17 Mar 2020, 6:32 pm Midhun Mohan, > wrote: > > > > > Hi all, > > > > > > I have a queue which will be filling up with realtime records of around > > > 20k records. Which is posting to an endpoint using Invokehttp > processor. > &

Re: Make invokehttp to process faster to process more than 20k records

; > 20k records. Which is posting to an endpoint using Invokehttp processor. > > > > currently the average throughput is for 10k records it takes around 20 > > minutes to complete the invokehttp processor posting. > > I Increased the concurrent thread to larger number whi

Re: Make invokehttp to process faster to process more than 20k records

Do anyone have better idea on this On Tue, 17 Mar 2020, 6:32 pm Midhun Mohan, wrote: > Hi all, > > I have a queue which will be filling up with realtime records of around > 20k records. Which is posting to an endpoint using Invokehttp processor. > > currently the average thr

Make invokehttp to process faster to process more than 20k records

Hi all, I have a queue which will be filling up with realtime records of around 20k records. Which is posting to an endpoint using Invokehttp processor. currently the average throughput is for 10k records it takes around 20 minutes to complete the invokehttp processor posting. I Increased

Invokehttp errors process first before original message

Hi all, I have a scenario here, Messages are flowing sequentially into an invoke HTTP processor. Let's say the first few messages fail and went to the failure state. Is there any way that I can rerun the errored message first then execute the rest of the message in the order. If so please let me

Re: Invokehttp

not with invokehttp but with any nifi processor is to check and process all possible outgoing relationships, and not just the "good" path as most junior developers tend to do. Best Regards, *Emanuel Oliveira* On Tue, Feb 25, 2020 at 8:31 PM Midhun Mohan wrote: > Hi > I have a

Invokehttp

Hi I have an implementation that calls the INVOKEHTTP processor more than 10 times in a minute. So if the endpoint in processor fails suddenly. Would I be able to reprocess the failed message on a priority basis before the next message? If so please let me know how can I do that --

Re: invokeHttp routing of exceptions like ConnectException and IOException to failure instead of retry

ccess" and "failure" relationship pair. InvokeHTTP uses that precedent to capture TCP oriented failures, and additionally provides relationships when the http protocol can provide more context. In short, the "failure" relationship captures TCP related problems. The &

invokeHttp routing of exceptions like ConnectException and IOException to failure instead of retry

Hi, While testing invokeHttp retry logic when the destination endpoint is offline, I learned that invokeHttp processor routes exceptions caused by the offline endpoint to the failure relationship instead of the retry relationship. That surprised me since those types of errors are exactly what I

InvokeHTTP support for sending a Useragent

Hi, I recently found that the InvokeHTTP processor does not send a User-agent header with the request. To solve this I filed issue NIFI- (yes, really that number ... on Friday the 13th ... ) and I put up a pull/merge request with a proposed fix. https://issues.apache.org/jira/browse/NIFI

Re: InvokeHttp - Response - Not readable

i tried with that user defined attribute as well earlier, but no luck :( -- Sent from: http://apache-nifi-developer-list.39713.n7.nabble.com/

Re: InvokeHttp - Response - Not readable

Have you tried adding a user-defined property to InvokeHttp with name of "Accept" and value of "application/json" ? Any user defined properties should be sent as headers. On Mon, Apr 8, 2019 at 10:11 PM Puspak wrote: > > Thanks Bryan , > > I sent the floe fi

Re: InvokeHttp - Response - Not readable

and that JavaScript is enabled. and please find the below properties those are set for my invokehttp .If possible please let me know i something wrong over there .i donot have a property Accept:application/json now but still the same issue. HTTP Method:GET Remote URL:http

Re: InvokeHttp - Response - Not readable

are expecting json back, then maybe something is wrong with your configuration in InvokeHttp... you added a user defined property for Accept = application/json ? On Mon, Apr 8, 2019 at 11:07 AM Puspak wrote: > > Thanks Bryan for the quick response . > > Below is the complete details of

Re: InvokeHttp - Response - Not readable

Thanks Bryan for the quick response . Below is the complete details of the response . Attribute Values Cache-Control no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Connection close Content-Length 294 Content-Type text/html; charset=utf-8 Date Mon, 08 Apr 2019 11:08:25 GMT Expires

Re: InvokeHttp - Response - Not readable

Hello, Can you provide more information about the response? what is the http status code? what is the body of the response? Can you make the same request using curl ? -Bryan On Mon, Apr 8, 2019 at 7:16 AM Puspak wrote: > > Hi team , > My invokehttp is making a get call

InvokeHttp - Response - Not readable

Hi team , My invokehttp is making a get call over http , but the response i am getting not able to read . when i am reading the flow file i can only see "No viewer is registered for this content type." I tried various option to get the json response , but no luck. approach i tried :

How to upload a file by using InvokeHTTP (multipart/form-data)?

Hi, I try to use InvokeHTTP processor to upload a file and got some error. I had a HTTP POST message that I tested by using Postman and everything ok. I try to implement in NIFI but I cannot change the Content-Type by using UpdateAttribute processor as I searched in the internet. Nifi still

Re: Getting Duplicate Flowfiles from InvokeHttp and QueryElasticsearchHttp

Bryan, Thanks so much! I get it now, and was able to find the setting and change it to behave the way that makes the most sense for me. I appreciate all your help, Martin -- Sent from: http://apache-nifi-developer-list.39713.n7.nabble.com/

Re: Getting Duplicate Flowfiles from InvokeHttp and QueryElasticsearchHttp

> > > Are you running a NiFi cluster of 2 nodes, or a standalone instance of > > NiFi? > > > > -Bryan > > > > On Mon, Mar 18, 2019 at 12:21 PM Martin Cooley > > > martin.cooley@ > > > wrote: > >> > >> If I configure an Invo

Re: Getting Duplicate Flowfiles from InvokeHttp and QueryElasticsearchHttp

t 12:21 PM Martin Cooley > martin.cooley@ > wrote: >> >> If I configure an InvokeHttp processor to query against an elasticsearch >> node, I should get one json object written to a flowfile. If I use the >> QueryElasticsearchHttp processor, if the query returns

Getting Duplicate Flowfiles from InvokeHttp and QueryElasticsearchHttp

If I configure an InvokeHttp processor to query against an elasticsearch node, I should get one json object written to a flowfile. If I use the QueryElasticsearchHttp processor, if the query returns two documents from the index, I should get two json objects, each written to their own flowfile

Re: InvokeHttp-1.6.0

Hello Vinod, The underlying library for InvokeHttp that we use to make the HTTP calls, OkHttp, removed these with their 3.1.0 release[1]. They were considered a "leaked implementation detail". There appears to be a workaround but that'd be a not insignificant amount of work to impleme

InvokeHttp-1.6.0

Hi Team, In InvokeHttp-1.0.0 processor I have response attributes as " *OkHttp-Received-Millis,OkHttp-Sent-Millis "* I am not able to find those attributes in invokehttp-1.6.0. Please Help me to get those attributes in version 1.6.0 also*.* -- With Regards, V

RE: SOAP Service through InvokeHTTP

It was pretty easy once I got the Xml structure correct. Hope this helps Bruce -Original Message- From: Mike Thomsen [mailto:mikerthom...@gmail.com] Sent: Saturday, March 24, 2018 4:17 AM To: dev@nifi.apache.org Subject: Re: SOAP Service through InvokeHTTP Been a while since I've done any

Re: SOAP Service through InvokeHTTP

xfa...@gmail.com> wrote: > I've only just subscribed to the dev@nifi.apache.org mailing list and > today > was my first time even knowing that a thing like 'maling lists' existed. > Regardless, I'm posting my question in hopes to seek out how you eventually > managed to get your InvokeH

Re: SOAP Service through InvokeHTTP

I've only just subscribed to the dev@nifi.apache.org mailing list and today was my first time even knowing that a thing like 'maling lists' existed. Regardless, I'm posting my question in hopes to seek out how you eventually managed to get your InvokeHTTP Processor to work with SOAP as I have

Re: Duplicate Hits From invokehttp

Hi V, Would you elaborate what you mean by duplicate response? Does it mean when a failed FlowFile at the 1st request is routed back to the same InvokeHTTP, sent as the 2nd request, and if the 2nd request succeeds, you get TWO duplicated output FlowFiles for the Response relationship? If your

Duplicate Hits From invokehttp

Hi, How to handle the duplicate responses from invokehttp. if i did not get the response from remote server, it is initiating the same request to the remote server and giving duplicate response,How to handle thiis scenario. thanks V -- Sent from: http://apache-nifi-developer-list

Re: SOAP Service through InvokeHTTP

how can i read data from soap service. What are the configuration properties and where can i set the soap url and wsdl url uisng invokehttp? -- Sent from: http://apache-nifi-developer-list.39713.n7.nabble.com/

Re: SOAP Service through InvokeHTTP

. -- View this message in context: http://apache-nifi-developer-list.39713.n7.nabble.com/SOAP-Service-through-InvokeHTTP-tp13129p14238.html Sent from the Apache NiFi Developer List mailing list archive at Nabble.com.

Re: SOAP Service through InvokeHTTP

this message in context: http://apache-nifi-developer-list.39713.n7.nabble.com/SOAP-Service-through-InvokeHTTP-tp13129p14237.html Sent from the Apache NiFi Developer List mailing list archive at Nabble.com.

Re: InvokeHTTP - no relationship invoked for 502 response

a GET with no incoming flow file? In > the former case you'd have two types of flow files to deal with (is it > request or response?), in the latter case the flow file would likely > only be an indication that a GET occurred, as it would have no > content, and if the retry route were c

Re: InvokeHTTP - no relationship invoked for 502 response

a "fake" request be generated for a GET with no incoming flow file? In the former case you'd have two types of flow files to deal with (is it request or response?), in the latter case the flow file would likely only be an indication that a GET occurred, as it would have no content, and if the retry

Re: InvokeHTTP - no relationship invoked for 502 response

hed a screenshot to show you what I mean. Looking at the code the only possible explanation for this would be that the incoming flowfile == null. Since my "InvokeHTTP" is a simple "GET" with no incoming flowfile I believe that the line at [1] is not being invoked as expected b

Re: InvokeHTTP - no relationship invoked for 502 response

Jeremy, The code implies that 502 responses (actually all 5xx responses) are routed to "retry" [1]. Are you not seeing that? Regards, Matt [1]

InvokeHTTP - no relationship invoked for 502 response

I'm monitoring some micro services that sit behind an Nginx reverse proxy. The idea is simple I want to fire off an alert if I get a "502 - Bad Gateway" response from Nginx which would mean that something has caused the micro service to crash and then have NiFi attempt to restart the micro

Re: Nifi InvokeHttp

Hi Selvam, Did you find a solution for this? Although the inline image couldn't be displayed for me, I assume the problem is how to invoke InvokeHttp using each setSpec.n attribute, and the n can vary. If so, you could design your flow differently, by splitting a XML into multiple flow-files

Nifi InvokeHttp

.1 setSpec.2 setSpec.3 Now i want to invoke InvokeHttp for above three records. how can i give dynamic values in remoteURL (http://test/setSpec.*) -- Selvam Raman "லஞ்சம் தவிர்த்து நெஞ்சம் நிமிர்த்து"

Re: SOAP Service through InvokeHTTP

lly open to fixing issues you may find and/or accepting PR's. If it > makes enough sense and is complete enough I have no problem contributing > it. > > Thanks, > Andrew > > [1] https://github.com/apsaltis/nifi-soap > > On Wed, Aug 24, 2016 at 7:40 PM, Jeff <jtsw...@gmail.

Re: SOAP Service through InvokeHTTP

contributing it. Thanks, Andrew [1] https://github.com/apsaltis/nifi-soap On Wed, Aug 24, 2016 at 7:40 PM, Jeff <jtsw...@gmail.com> wrote: > Hello, > > With InvokeHTTP, you can add dynamic properties, which will be sent in the > request as headers. You can use dynamic proper

Re: SOAP Service through InvokeHTTP

Hello, With InvokeHTTP, you can add dynamic properties, which will be sent in the request as headers. You can use dynamic properties to set values for the Content-Type and SOAPAction headers, just use the header names for the names of the dynamic properties. InvokeHTTP lets you control the HTTP

SOAP Service through InvokeHTTP

Hello, I am looking to do a SOAP Web service call and was told invokeHTTP may be able to work. Wonder how I would be able to do this. For example, using curl I could invoke SOAP like the below: curl -X POST -H "Content-Type: text/xml" -H "SOAPAction: "http:/

Re: TLSv1.2 in GetHttp vs. InvokeHttp

D EF69 > On Jul 14, 2016, at 1:25 PM, Andy LoPresto <alopre...@apache.org> wrote: > > Larry, > > Thanks for pointing this out. I just fixed the same issue in PostHTTP [1][2], > but as you correctly asserted InvokeHTTP handles this in a better mechanism. > GetHTTP and

Re: TLSv1.2 in GetHttp vs. InvokeHttp

Larry, Thanks for pointing this out. I just fixed the same issue in PostHTTP [1][2], but as you correctly asserted InvokeHTTP handles this in a better mechanism. GetHTTP and PostHTTP were “legacy” processors originally designed to move flowfiles between systems over HTTP, while InvokeHTTP

Re: TLSv1.2 in GetHttp vs. InvokeHttp

onSocketFactory(sslContext, > new String[]{"TLSv1"}, null, SSLConnectionSocketFactory. > BROWSER_COMPATIBLE_HOSTNAME_VERIFIER); > > I did not see anything similar in InvokeHttp so I went ahead and changed my > processors to use that and it worked. GetHttp doesn't really o

TLSv1.2 in GetHttp vs. InvokeHttp

sslsf = new SSLConnectionSocketFactory(sslContext, new String[]{"TLSv1"}, null, SSLConnectionSocketFactory. BROWSER_COMPATIBLE_HOSTNAME_VERIFIER); I did not see anything similar in InvokeHttp so I went ahead and changed my processors to use that and it worked. GetHttp doesn't really offe

[GitHub] nifi pull request #398: NIFI-1751 Added proxy authentication in InvokeHttp p...

Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/398 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] nifi issue #398: NIFI-1751 Added proxy authentication in InvokeHttp processo...

Github user apiri commented on the issue: https://github.com/apache/nifi/pull/398 @pvillard31 Sounds fair. Will get this incorporated. Thanks for the contribution. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If

[GitHub] nifi issue #398: NIFI-1751 Added proxy authentication in InvokeHttp processo...

Github user pvillard31 commented on the issue: https://github.com/apache/nifi/pull/398 Yep, not sure it's worth it. I think it is fine to let the PR as is. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project

[GitHub] nifi issue #398: NIFI-1751 Added proxy authentication in InvokeHttp processo...

Github user apiri commented on the issue: https://github.com/apache/nifi/pull/398 Actually, I think the Response#priorResponse probably doesn't apply to our case after thinking about it a bit more. The key way to avoid the issues seen is a flag/counter within that authenticator to

[GitHub] nifi issue #398: NIFI-1751 Added proxy authentication in InvokeHttp processo...

Github user pvillard31 commented on the issue: https://github.com/apache/nifi/pull/398 Hey @apiri, Many thanks for the review! Regarding HTTPS, at the time I submitted the PR I was testing it with CCProxy (on Windows computer). I can't test it again with this setup

[GitHub] nifi issue #272: NIFI-1620 Allow empty Content-Type in InvokeHTTP processor

Github user JPercivall commented on the issue: https://github.com/apache/nifi/pull/272 Thanks for the assist @apiri --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and

[GitHub] nifi issue #398: NIFI-1751 Added proxy authentication in InvokeHttp processo...

Github user apiri commented on the issue: https://github.com/apache/nifi/pull/398 Hey @pvillard31, I did a review of this and it seems to work mostly well using Squid with the following config: ``` auth_param basic program

[GitHub] nifi pull request #272: NIFI-1620 Allow empty Content-Type in InvokeHTTP pro...

Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/272 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] nifi issue #272: NIFI-1620 Allow empty Content-Type in InvokeHTTP processor

Github user apiri commented on the issue: https://github.com/apache/nifi/pull/272 @taftster @JPercivall I'll aid in the assist and wrap this up as I have been scanning through PRs and can merge in. --- If your project is set up for it, you can reply to this email and have your reply

[GitHub] nifi issue #272: NIFI-1620 Allow empty Content-Type in InvokeHTTP processor

Github user JPercivall commented on the issue: https://github.com/apache/nifi/pull/272 @taftster thanks for taking another look, yup I can merge this when I get a chance. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well.

[GitHub] nifi issue #272: NIFI-1620 Allow empty Content-Type in InvokeHTTP processor

Github user taftster commented on the issue: https://github.com/apache/nifi/pull/272 I'm happy with this PR. Thanks @pvillard31 for all the effort and seeing this through many changes and discussions. @JPercivall can you still merge this? I'm in between environments right

[GitHub] nifi issue #272: NIFI-1620 Allow empty Content-Type in InvokeHTTP processor

Github user pvillard31 commented on the issue: https://github.com/apache/nifi/pull/272 It should be OK, let me know if not. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature

Re: [GitHub] nifi issue #272: NIFI-1620 Allow empty Content-Type in InvokeHTTP processor

I added a comment to the JIRA ticket associated with this pull request. I think there should be discussion / buy-in from others on the aestetics of introducing a new processor property for this edge case. Instead, I think the goals of this request could be fulfilled without strictly introducing

[GitHub] nifi pull request #272: NIFI-1620 Allow empty Content-Type in InvokeHTTP pro...

Github user taftster commented on a diff in the pull request: https://github.com/apache/nifi/pull/272#discussion_r67284145 --- Diff: nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/InvokeHTTP.java --- @@ -761,24

[GitHub] nifi pull request #272: NIFI-1620 Allow empty Content-Type in InvokeHTTP pro...

Github user taftster commented on a diff in the pull request: https://github.com/apache/nifi/pull/272#discussion_r67283832 --- Diff: nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/InvokeHTTP.java --- @@ -215,14

[GitHub] nifi issue #272: NIFI-1620 Allow empty Content-Type in InvokeHTTP processor

Github user JPercivall commented on the issue: https://github.com/apache/nifi/pull/272 @taftster I'll let you finish it up tonight if you have time since you've already had eyes on it. If you're not able to, I'll take a look tomorrow. --- If your project is set up for it, you can

[GitHub] nifi issue #272: NIFI-1620 Allow empty Content-Type in InvokeHTTP processor

Github user taftster commented on the issue: https://github.com/apache/nifi/pull/272 I can try to look at it tonight. But no problems if you want to step in. > On Jun 15, 2016, at 10:51 AM, Joe Percivall wrote: > > @taftster will you have

[GitHub] nifi issue #272: NIFI-1620 Allow empty Content-Type in InvokeHTTP processor

Github user JPercivall commented on the issue: https://github.com/apache/nifi/pull/272 @taftster will you have time to finish up this review for 0.7.0 or do you want me to finish it? --- If your project is set up for it, you can reply to this email and have your reply appear on

InvokeHTTP is a Final Class

I was looking at using InvokeHTTP as the base for a class that would interact with our API. I wanted to to have the processors make some assumptions that are true with our API but not HTTP in general (Mostly our method of Authentication). This class looked well suited for this (the class is well

Re: Dynamic URLs using InvokeHttp from an array

: > I looked into the links, but they didn't quite give me what I was looking > for. Instead, I thought I would try a different route. I "borrowed" the > code from InvokeHttp and created another processor called InvokeHttpLooped > (I know...not very original). > > I mod

Re: Dynamic URLs using InvokeHttp from an array

I looked into the links, but they didn't quite give me what I was looking for. Instead, I thought I would try a different route. I "borrowed" the code from InvokeHttp and created another processor called InvokeHttpLooped (I know...not very original). I modified it so that I could

Re: Dynamic URLs using InvokeHttp from an array

eveloper-list.39713.n7.nabble.com/Dynamic-URLs-using-InvokeHttp-from-an-array-tp8638p8658.html > Sent from the Apache NiFi Developer List mailing list archive at > Nabble.com. >

Re: Dynamic URLs using InvokeHttp from an array

you'd end up with 10 flowfiles that could be sent to InvokeHTTP. That might be a fun way to solve this. :) On Thu, Mar 31, 2016 at 9:55 AM, Adam Taft <a...@adamtaft.com> wrote: > One (possibly bad) idea would be to try and loop your flow around the > UpdateAttribute processor using RouteOnAt

Re: Dynamic URLs using InvokeHttp from an array

://apache-nifi-developer-list.39713.n7.nabble.com/Dynamic-URLs-using-InvokeHttp-from-an-array-tp8638p8658.html Sent from the Apache NiFi Developer List mailing list archive at Nabble.com.

Re: Dynamic URLs using InvokeHttp from an array

uot;step 1" then set $foo = "step 2"; if $foo == "step 2" then set $foo = "step 3"; ... if $foo == "step n" then set $foo = "finished"; The next part would be RouteOnAttribute, which would read the value of $foo and if set to "finished"

Re: Dynamic URLs using InvokeHttp from an array

This sounds like a good candidate for the `ExecuteScript` processor. Matt Burgess has written some good tutorials on using that here [1] [2]. You could also write a custom processor that extends `InvokeHTTP` and uses the new state management features [3] to keep a counter value, an iteration

  1   2   >