Well, in fact, I try to exchange with an external API which is expecting a
POST request without any Content-Type attribute:



*"You provided a non-empty HTTP "Content-Type" header
("application/json").  This API function requires that the header be
missing or empty."*
So in addition to my previous message, I'd suggest authorizing an empty
Content-Type value which would lead to request without this header property.
I'm going to create a JIRA for that.


2016-03-11 12:56 GMT+01:00 Pierre Villard <[email protected]>:

> Hi,
>
> Would it make sense to add a property "body" allowing the user to manually
> set the body of the request for PUT/POST requests?
>
> At the moment, the body of the request seems to be only set with the
> content of incoming flow files. But it is possible to use this processor
> without incoming relationship. It would be useful to be able to set the
> body manually.
>
> The behaviour would be: if there is an incoming relationship, the incoming
> flow file content is used whatever the property "body" is, and if there is
> no incoming relationship, the request body is based on the property value.
>
> What do you think?
>
> Pierre
>
>

Reply via email to