Hello, The "Attributes to Send" property is a regular expression, so you should be able to put ".*" to send all flow file attributes as headers, or you can make a pattern that matches a group of attributes that follow some naming convention.
Thanks, Bryan On Mon, Sep 10, 2018 at 6:22 AM, Dnyaneshwar Pawar <[email protected]> wrote: > Hi All, > > > > We want to pass the custom headers to third party rest application > through InvokeHttp processor. We know this can be achieved by using > ‘attribute to send’ and ‘dynamic properties’, however both of these needs > key name. While on our case we don’t know key/value or even how many headers > would present in request. > > So, the typical requirement is , how to pass/carry Header 1 … Header > N, from end user, as it is through InvokeHttp processor? > > > > Thank You! > > > > Regards, > > Dnyaneshwar Pawar > > > > DISCLAIMER > ========== > This e-mail may contain privileged and confidential information which is the > property of Persistent Systems Ltd. It is intended only for the use of the > individual or entity to which it is addressed. If you are not the intended > recipient, you are not authorized to read, retain, copy, print, distribute > or use this message. If you have received this communication in error, > please notify the sender and delete all copies of this message. Persistent > Systems Ltd. does not accept any liability for virus infected mails.
