Hi Wyllys, Sorry to hear you are having trouble with this processor. Can you please provide a more detailed example of an incoming flowfile and what your expected output is compared to what is currently happening? Based on my understanding, the flowfile attributes are only sent as request headers, and that can be controlled using the regular expression value of “Attributes to Send”. I believe only the flowfile content is sent as the request body when using PUT or POST. Thanks.
Andy LoPresto [email protected] [email protected] PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > On Jun 18, 2019, at 3:01 PM, Wyllys Ingersoll > <[email protected]> wrote: > > > it would be nice to be able to exclude attributes from the message body when > doing a PUT or POST in the invokeHTTP processor. Currently, there's no way > to selectively choose which attributes go into the message body without using > a replaceText processor in front of it, but that completely removes those > attributes from being used later which is not always the desirable. > > There are lots of situations where it would be nice to be able to use some > flow attributes just in the request header or for other parts of the > processor configuration without including them in the message body itself. > For example, taking an authentication token that is carried along as a flow > attribute so it can be used in an authorization header and NOT included in > the body of the request. > > In general, invokeHTTP needs to allow for more control over the format and > content of the message body being sent. > > -Wyllys Ingersoll >
