question Nifi InvokeHttp Content-Type with GET in Archives of Support Questions (Read Only)

Nifi InvokeHttp Content-Type with GET

frankmarit — Fri, 09 Sep 2016 03:39:53 GMT

The web service I'm calling requires the Content-Type header to be set to application/json, but it appears the InvokeHttp processor only sets this header if it is a POST or PUT request. Is there any way to set this header for GET requests?

Re: Nifi InvokeHttp Content-Type with GET

dpinkston — Mon, 19 Aug 2019 08:05:14 GMT

@Frank Maritato

Have you looked at adding a dynamic property? If you take a look here: https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi.processors.standard.InvokeHTTP/

"Attributes to send" is where you will want this. So in your nifi processor it should look like the image attached, can you try that?

Re: Nifi InvokeHttp Content-Type with GET

frankmarit — Fri, 09 Sep 2016 04:32:17 GMT

Thanks for the answer. What you posted didn't work, but I did play with and eventually got it. What I had to do was have an UpdateAttribute processor before my InvokeHTTP that sets an attribute called "Content-Type", then in InvokeHTTP, set "attributes to send" to "Content-Type" and it worked.

Thanks!

Re: Nifi InvokeHttp Content-Type with GET

oka — Fri, 24 Apr 2026 12:08:39 GMT

Do you know how to retrieve the content type from the message properties when using ConsumeJMS?