nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Otto Fowler <ottobackwa...@gmail.com>
Subject Re: The difference between PostHTTP and GetHTTP wrt headers
Date Fri, 16 Mar 2018 02:40:33 GMT
So looking at it, the standard way would be dynamic properties.  Thank you
Andy.


On March 15, 2018 at 22:30:33, Otto Fowler (ottobackwards@gmail.com) wrote:

I’m actually looking at doing a web service processor , that would support
setting custom headers, and I want it to be “standard”.
I’ll look at the InvokeHTTP.


On March 15, 2018 at 15:57:33, Andy LoPresto (alopresto@apache.org) wrote:

Both of these are legacy processors introduced early on in NiFi’s
development and intended for moving data between NiFi instances. I would
recommend you use InvokeHTTP, which is a more modern and full-featured
processor and can perform both GET and POST requests.


Andy LoPresto
alopresto@apache.org
*alopresto.apache@gmail.com <alopresto.apache@gmail.com>*
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69

On Mar 15, 2018, at 12:47 PM, Otto Fowler <ottobackwards@gmail.com> wrote:

Can someone explain or confirm why GetHTTP uses Dynamic Properties for
setting custom headers in http requests but PostHTTP uses a Property with a
Regex to pull flow file attributes?

Is it due to the forbidden input?

Thanks

ottO

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message